TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
DocumentationTDSQL-C for MySQLKernel FeaturesKernel Version Release NotesDatabase Proxy Version Release Notes
Database Proxy Version Release Notes
Last updated: 2025-04-01 15:11:06
This document presents the update notes of the TDSQL-C for MySQL database proxy version.
Note:
If the kernel version requirements of TDSQL-C for MySQL are not met, you can upgrade the database kernel version first as instructed in Upgrading Kernel Minor Version. For information on the release dates of various database proxy versions, please refer to the Database Proxy Version Release Dates.
Version | TDSQL-C for MySQL Kernel Version Requirement | Description |
1.3.16 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Bug fixes Fixed the issue that executing prepared statements at a read-only address could occasionally result in errors. Addressed the problem that enabling connection pooling may lead to exceptions in Capabilities Flags. Fixed a rare occurrence of connection disruptions during frequent changes in replication delay on read-only instances. |
1.3.15 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Performance optimizations Optimized the memory usage under high load and solved the problem that the memory may be at high level for a long time. Bug fixes Fixed the issue that the momentary disconnection prevention feature may fail. |
1.3.14 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Feature updates Now the SHOW BINLOG EVENTS statement and the SHOW BINARY LOGS statement will be routed to a primary instance. Optimized the issue of excessive memory usage when returned large packets were queried. Bug fixes Fixed the occasional issue that the character set sorting of handshake packets was inconsistent with the back-end database. Fixed an issue that a primary-secondary switch on the primary database sometimes caused a connection interruption to the read-only address. Fixed an issue that the authentication may fail when an account's designated IP matched multiple accounts. |
1.3.13 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Feature updates Now system variables related to select binlog will be sent to the primary database for execution. Added new high-availability detection statements to reduce migrations caused by fault misjudgment. Optimized the memory usage of the database proxy kernel in multi-threaded scenarios. Bug fixes Fixed an issue that an error was reported when a prepare statement was executed in a read-only transaction. Fixed a performance issue caused by frequent connection attempts with an incorrect username. After transaction splitting is enabled, commit and rollback statements will be routed to all nodes to prevent pending uncommitted transactions on RO nodes. |
1.3.12 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Feature updates Transferred the reading of system variables to the primary database for execution. Bug fixes Fixed the issue that partial connections get stuck for a too long period when a large number of connections trigger anti-flapping. Fixed the issue that partial connections are not cut off as expected when a large number of connections trigger load rebalancing. Fixed the issue of consistency loss caused by the client sending a com_reset command. |
1.3.10 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Bug fixes Resolved an issue where handling response packets could result in exceptions when encountering specific messages. |
1.3.8 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Feature updates Enhanced support for updated functions in MySQL versions 5.7 and 8.0. Optimized parser caching to reduce the likelihood of Out of Memory (OOM) errors under complex SQL queries. Introduced traffic monitoring metrics for database proxies. Implemented dynamic load balancing capabilities. Introduced anti-flapping features. |
1.3.7 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Bug fixes Fixed the routing error of the select for update statement in some cases. Modified the select @@read_only statement and made it possible to be routed to the source database. This prevents some frameworks that use read_only flags from misjudging the database proxy as unwritable. Fixed the database proxy node exceptions caused by a database instance HA in some scenarios. |
1.3.5 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Bug fixes Resolved the issue of decreased and fluctuating read performance in read-only instances under high concurrency scenarios. |
1.3.4 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Bug fixes Resolved the issue of incomplete data returned by the show processlist command. |
1.3.3 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Bug fixes Fixed the issue where an error was reported when the session connection pool reused connections to send change_user to the backend, and the issue where the PREPARE statement was not correctly handled by the database proxy after a new connection was established. Fixed the issue where the execute statement lacked parameter types. |
1.2.1 | - | Feature updates Supported MySQL 5.7/8.0. Supported cluster deployment, enabling the deployment of multiple instances in a single database proxy. Supported read/write separation along with corresponding weight configuration. Supported the failover feature, rerouting read requests to the read-write instance in case of read-only instance exceptions. Supported the load balancing feature to address uneven connection counts among proxy nodes. Supported using the hint syntax to specify routing nodes. Supported session-level connection pooling, handling scenarios where frequent connections need to be established with the database in short lived connection-based businesses. Database proxy supported saving connections and reusing them for subsequent connection attempts. Supported hot loading, allowing online modifications of configurations without the need of restarting the dedicated database proxy. Supported the reconnection feature for read-only instances. In scenarios involving long lived connections, the database proxy will automatically re-establish a connection and restore the routing nodes if a read-only instance is restarted or a read-only instance is added. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No