Release Notes
Product Introduction
- Overview
- Scenarios
- Product Architecture
- Instance Types
- Compatibility Notes
- Usage Recommendations
Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Columnar Read-Only Analysis Engine Features
Billing
Getting Started
- Creating Instances
- Connect to Instances
User Guide
- Use Limits
- Operation Overview
- Data Migration
- Data Subscription
- Instance Management
- Configuration Change
- Multi-AZ Deployment
- Disaster Recovery Instance
- Monitoring and Alarms
- Parameter Configuration
- Account Management
- Network and Security
- Cold Data Archiving
- Backup and Restoration
- Log Center
- Enabling the Audit Service
- Tag Management
- Serverless Service
- Read-Only Analysis Instance
Use Cases
Developer Guide
- Developer Guide (MySQL Compatibility Mode)
- Developer Guide (HBase Compatibility Mode)
Performance Tuning
- Performance Tuning Overview
- SQL Tuning
- DDL Tuning
Performance White Paper
Troubleshooting
- Performance
- Transaction
API Reference
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Security Group APIs
- Task APIs
- Data Security Encryption APIs
- Account APIs
- Backup APIs
- Restore APIs
- Parameter APIs
- Database APIs
- Log APIs
- Other APIs
- Data Types
- Error Codes
General Reference
- System Architecture
- SQL Reference
- Database Parameter Description
- TPC-H benchmark data model reference
- Error Code Information
Security and Compliance
FAQs
- Selection Related
- Features
- Connecting and Logging In
- Backup
- Restoration
- Account Permission
- Performance Memory
- Cold Data Archiving
Agreements
Contact Us
Glossary

tdsql_transaction_max_participants

Download

Focus Mode

Font Size

Last updated: 2026-05-26 17:00:08

AI-Translated

Feature Description
tdsql_transaction_max_participants specifies the maximum number of participants (ReplicationGroup) allowed in a single transaction.
For example, if the number is set to 100, at most 100 participants can be involved in a transaction. This ensures that the transaction scale remains within a controllable range, avoiding performance and resource consumption issues caused by oversized transactions.
Attribute Description
Required
Description
Parameter Type
UINT
Default Value
10000
Value Range
1 ~ 4294967295
Effective Scope
GLOBAL
Restart Required
Yes

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

tencent cloud

TDSQL Boundless

tdsql_transaction_max_participants

Feature Description

Attribute Description

Help and Support

Required	Description
Parameter Type	UINT
Default Value	10000
Value Range	1 ~ 4294967295
Effective Scope	GLOBAL
Restart Required	Yes