Database Proxy Version | Requirements of TDSQL-C for MySQL Kernel | Description |
1.3.22 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Feature updates Added Response Time statistics for database proxy links. Issue Fixes Fixed the kernel exception issue in multi-statement scenarios. |
1.3.21 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Feature updates Added multiple kernel monitoring metrics, including Prepare and Execute call statistics. Improved the stability of momentary disconnection prevention under high-concurrency traffic. Issue Fixes Fixed the issue where the momentary disconnection prevention feature occasionally caused process crashes under extreme scenarios. Fixed the memory management logic related to the momentary disconnection prevention feature and optimized the memory leak issue of the feature. |
1.3.20 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Issue Fixes Fixed the issue where connections might not be restored with a low probability after momentary disconnection prevention is enabled. Fixed the issue where momentary disconnection prevention failed after consistency configuration was set. |
1.3.19 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Issue 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 | Issue 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 | Issue Fixes Fixed the issue where errors might occur with a low probability when precompiled statements are executed on a read-only address. Fixed the issue where Capabilities Flags might become abnormal after the connection pool is enabled. Fixed the issue where connections might be abnormally disconnected with a low probability when the replication delay of a read-only instance fluctuates frequently. |
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 optimization Optimized memory usage under high loads, resolving the potential issue of memory remaining at a high level for extended periods. Issue Fixes Fixed the issue where momentary disconnection prevention might fail with a certain probability. |
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 The SHOW BINLOG EVENTS and SHOW BINARY LOGS statements are now routed to the primary instance. Optimized the issue where excessive memory usage might occur when queries return large packets. Issue Fixes Fixed the issue where the character set collation in the handshake packet occasionally did not match that of the backend 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 the issue where authentication might fail when an IP address specified for an account matches 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 are sent to the primary databases for execution. Added new high-availability detection statements to reduce migrations caused by false-positive failures. Optimized the memory usage of the database proxy kernel in multi-threaded scenarios. Issue Fixes Fixed the issue that an error was reported when a precompiled statement was executed in a read-only transaction. Fixed the performance issue that occurred when connections were frequently established using 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. |
Database Proxy Version | Requirements of TDSQL-C for MySQL Kernel | Description |
1.4.7 | 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 Supports column-format storage node routing and automatic HTAP forwarding. Issue Fixes Fixed the issue where the momentary disconnection prevention or transaction-level connection pool feature behaved abnormally when variables used by the application or database names contained special characters. Fixed the issue where the transaction-level connection pool did not correctly reset the sql_select_limit session variable when connections were reused, which led to incomplete query result sets. Fixed the issue where instance memory leaks could occur when an application's execution of a prepared Statement failed. Fixed the issue where the database proxy might return an incorrect database version number during the handshake phase after a client connects to it. Fixed the issue where connections in the transaction-level connection pool were not reclaimed in a timely manner under specific transaction scenarios. Fixed the issue where the database proxy parsed queries incorrectly when a client sent multi-statement queries. Fixed the issue where momentary disconnection prevention caused process crashes under specific scenarios. |
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 and 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. |
Database Proxy Version | Requirements of TDSQL-C for MySQL Kernel | 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 Now, read operations for system variables are sent to the primary databases for execution. Issue Fixes Fixed the issue where some connections might be stuck for an excessively long time when momentary disconnection prevention was triggered by a large number of connections. Fixed the issue where some connections were not disconnected as expected when a large number of connections triggered a load rebalance. Fixed the issue where consistency was invalidated because the client sent a COM_RESET_CONNECTION packet. |
1.3.10 | TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6 TDSQL-C for MySQL 8.0 ≥ 3.1.6 | Issue Fixes Fixed the issue where an exception might occur when response packets are processed and specific packets are encountered. |
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 Added support for more functions that were updated in the new versions of MySQL 5.7 and 8.0. Optimized the parser cache to reduce the probability of OOM when a large volume of complex SQL is processed. Added traffic monitoring metrics for the database proxy. 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 | Issue 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 primary 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 issue where database proxy node exceptions were caused by 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 | Issue Fixes Optimized the issue of read performance degradation and fluctuation on 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 | Issue 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 | Issue 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 Supports MySQL 5.7/8.0 versions. Supports cluster deployment, allowing multiple instances to be deployed under a single database proxy. Supports read/write splitting and weight configuration under read/write splitting. Supports the failover feature. When a read-only instance becomes abnormal, read requests are sent to the read-write instance. Supports the CLB feature to handle scenarios where connection counts are unbalanced across proxy nodes. Supported using a hint to specify the destination node for routing. Supports the session-level connection pool feature to handle scenarios where frequent connections to the database are established in non-persistent connection services. The database proxy saves connections and reuses them when a new connection needs to be established. Supports hot reloading. All configurations can be changed online without restarting the database proxy. Added the reconnection feature for read-only instances. In scenarios with persistent connections, when a read-only instance is restarted or a new read-only instance is added, the database proxy automatically re-establishes connections to the read-only instances to restore routing nodes. |
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