Database Proxy Version Release Notes

Last updated: 2025-11-26 11:31:26

Database Proxy Version Release Notes

Last updated: 2025-11-26 11:31:26

This document presents the update notes of the TDSQL-C for MySQL database proxy version.
Note:
If the version does not meet the requirements of TDSQL-C for MySQL kernel version, you can first upgrade the database kernel version. For more details of operations, you can view upgrade kernel minor version.
For the release time of each database proxy version, you can view Database Proxy Version Release Time.
For the database proxy version, note that versions starting with 1.4 are preview versions, certain versions starting with 1.3 (specifically 1.3.13 and later versions) are stable versions, certain versions starting with 1.3 (specifically 1.3.12 and earlier versions) are outdated versions, and versions earlier than 1.3 are used during open beta and are no longer updated.
Stable Version Update Description
Update Description of the Version with New Features
Update Description of the Outdated Version
Version
TDSQL-C for MySQL Kernel Version Requirement
Description
1.3.19
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 the momentary disconnection prevention feature might cause incorrect character sets in some old connections or read consistency failure.
Fixed the issue that function calls on MySQL 8.0 instances were sometimes routed to the primary database after new read-only instances were added to the database proxy.
1.3.17
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 of errors that sometimes occurred when a read-only transaction was enabled after the transaction split feature was enabled.
Fixed the issue of character set errors that might occur during connection reuse after the connection pool was enabled.
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.
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 the issue that the connection to the read-only address of a source database with a read-write address was interrupted during a source-replica switch.
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
﻿System variables related to SELECT binlog will be sent to the source 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 the issue that an error was reported when a precompiled statement was executed in a read-only transaction.
Fixed a performance issue caused by frequent connection attempts with an incorrect username.
Fixed the issue that uncommitted transactions existed on read-only nodes because COMMIT and ROLLBACK statements were routed to all nodes after transaction split was enabled.
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 failure caused by the COM_RESET_CONNECTION message sent by the client.
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.
Supported momentary disconnection prevention during in-place restart and upgrades for the source instance.
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 issue of route errors that occurred when the SELECT...FOR UPDATE statement was executed in some cases.
The SELECT @@read_only statement will be routed to the source database to avoid using the read_only tag under certain frameworks, preventing the system to mistakenly determine that the database proxy is 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  
Fixed the issue that the returned data of SHOW PROCESSLIST was incomplete.
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 that an error may occur during statement precompilation under a session-level connection pool.
Fixed the issue that an error may occur during statement precompilation.
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 a hint to specify the destination node for routing.
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.
Database Proxy Version
Requirements of TDSQL-C for MySQL Kernel
Description
1.4.5
TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6
TDSQL-C for MySQL 8.0 ≥ 3.1.6
Read-only analysis engine version ≥ 2.2410.4.0
Feature updates
Supported the failover of LibraDB engine nodes to ordinary read-only nodes.
Supported LibraDB engine nodes participating in read-write separation load balancing as read-only nodes.
1.4.4
TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6
TDSQL-C for MySQL 8.0 ≥ 3.1.6
Read-only analysis engine version ≥ 2.2410.4.0
Feature updates
It supports integrating instances of the read-only analysis engine LibraDB into the read-write separation of the database proxy and fault elimination.
Supported using the hint /* to ap */ in SQL statements to route SQL statements to a read-only analysis engine instance.
Version
TDSQL-C for MySQL Kernel Version Requirement
Description
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 failure caused by the COM_RESET_CONNECTION message sent by the client.
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.
Supported momentary disconnection prevention during in-place restart and upgrades for the source instance.
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 issue of route errors that occurred when the SELECT...FOR UPDATE statement was executed in some cases.
The SELECT @@read_only statement will be routed to the source database to avoid using the read_only tag under certain frameworks, preventing the system to mistakenly determine that the database proxy is 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  
Fixed the issue that the returned data of SHOW PROCESSLIST was incomplete.
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 that an error may occur during statement precompilation under a session-level connection pool.
Fixed the issue that an error may occur during statement precompilation.
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 a hint to specify the destination node for routing.
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

Feedback

Version	TDSQL-C for MySQL Kernel Version Requirement	Description
1.3.19	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 the momentary disconnection prevention feature might cause incorrect character sets in some old connections or read consistency failure. Fixed the issue that function calls on MySQL 8.0 instances were sometimes routed to the primary database after new read-only instances were added to the database proxy.
1.3.17	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 of errors that sometimes occurred when a read-only transaction was enabled after the transaction split feature was enabled. Fixed the issue of character set errors that might occur during connection reuse after the connection pool was enabled.
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.
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 the issue that the connection to the read-only address of a source database with a read-write address was interrupted during a source-replica switch. 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 System variables related to SELECT binlog will be sent to the source 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 the issue that an error was reported when a precompiled statement was executed in a read-only transaction. Fixed a performance issue caused by frequent connection attempts with an incorrect username. Fixed the issue that uncommitted transactions existed on read-only nodes because COMMIT and ROLLBACK statements were routed to all nodes after transaction split was enabled.
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 failure caused by the COM_RESET_CONNECTION message sent by the client.
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. Supported momentary disconnection prevention during in-place restart and upgrades for the source instance.
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 issue of route errors that occurred when the SELECT...FOR UPDATE statement was executed in some cases. The SELECT @@read_only statement will be routed to the source database to avoid using the read_only tag under certain frameworks, preventing the system to mistakenly determine that the database proxy is 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 Fixed the issue that the returned data of SHOW PROCESSLIST was incomplete.
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 that an error may occur during statement precompilation under a session-level connection pool. Fixed the issue that an error may occur during statement precompilation.
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 a hint to specify the destination node for routing. 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.

Database Proxy Version	Requirements of TDSQL-C for MySQL Kernel	Description
1.4.5	TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 Read-only analysis engine version ≥ 2.2410.4.0	Feature updates Supported the failover of LibraDB engine nodes to ordinary read-only nodes. Supported LibraDB engine nodes participating in read-write separation load balancing as read-only nodes.
1.4.4	TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 Read-only analysis engine version ≥ 2.2410.4.0	Feature updates It supports integrating instances of the read-only analysis engine LibraDB into the read-write separation of the database proxy and fault elimination. Supported using the hint /* to ap */ in SQL statements to route SQL statements to a read-only analysis engine instance.

tencent cloud