Database Proxy Version Release Notes

Last updated: 2025-12-02 17:16:01

Database Proxy Version Release Notes

Last updated: 2025-12-02 17:16:01

This document describes the kernel version updates of the TencentDB for MySQL database proxy.
Note: 
If the MySQL kernel version requirements are not met, you can upgrade the kernel version of your database first as instructed in Upgrading Kernel Minor Version.
Regarding the database proxy versions, please be advised that versions beginning with 1.4 are beta, versions starting with 1.3 are deemed stable, and versions below 1.3 are categorized as public beta versions and will no longer receive updates.
The instance architectures supporting database proxy’s momentary disconnection prevention capabilities include MySQL dual-node (high availability edition) and MySQL triple-node. 
Release Notes for the Stable Version
Release Notes for Beta Version
Database Proxy Version
Release Date
MySQL Kernel Version Requirements
Description
1.3.20
2025-11
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Only the version was updated, and the supported capabilities were not changed.
1.3.19
2025-7
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Bug fixes
Fixed the issue that the momentary disconnection prevention feature might cause incorrect connection character sets.
1.3.17
2025-5
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue where errors occasionally occurred during read-only transaction initiating after transaction splitting is enabled. 
Addressed the issue where character set errors may occur during connection reuse after the connection pool is enabled.
1.3.16
2025-3
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
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 the issue that the connection might be interrupted when the replication delay of a read-only instance changed frequently after delayed read-only instance removal was enabled.
1.3.15
2024-12
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Performance optimizations
Optimized memory usage under high load conditions, addressing the issue of prolonged high memory utilization.
Fixes
Resolved the issue where the anti-disconnection feature occasionally failed.
1.3.14
2024-11
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
The statements SHOW BINLOG EVENTS and SHOW BINARY LOGS are now routed to the root instance.
Optimized the issue that querying large messages may result in excessive memory consumption.
Fixes
Fixed the occasional inconsistency between the character set sorting of the handshake messages and the backend databases.
Fixed the issue that the primary-secondary switch in the primary database may cause interruption in the read-only address connection.
Fixed the issue of the potential authentication failure when a specified IP address matches multiple accounts simultaneously.
1.3.13
2024-8
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
﻿System variables related to SELECT binlog will be sent to the primary database for execution.
Added new high-availability detection statements to reduce the migration caused by false fault detections.
Optimized the memory usage of the database proxy kernel in multi-threading scenarios.
Fixes
Fixed the issue that an error was reported when a precompiled statement was executed in a read-only transaction.
Fixed the performance issue caused by frequent connection establishment 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
2024-6
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
The SHOW VARIABLES statement will be sent to the primary database for execution.
Fixes
Fixed the issue that a large number of connections triggering momentary disconnection prevention could cause some connections to be stuck for too long.
Fixed the issue that a large number of connections triggering re-load balancing could cause some connections to fail to be broken as expected.
1.3.11
2024-5
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue that too many accounts could lead to connection failures.
Note:
Version 1.3.12 already includes this fix, so it is recommended to upgrade to 1.3.12 directly.
1.3.10
2024-3
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue that encountering specific messages during message processing could cause anomalies.
1.3.9
2024-1
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue that annotations in multi-statements caused incorrect parsing.
1.3.8
2023-9
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
Supports more functions updated in MySQL 5.7 and 8.0.
Optimized the parser cache to reduce OOM probability under a large number of complex SQL statements.
Added traffic monitoring metrics for the database proxy.
Supports the dynamic CLB feature.
Fixes
Fixed the issue that the momentary disconnection prevention feature might fail for some connections under a high connection count.
1.3.7
2023-4
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
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, causing the system to mistakenly determine that the database proxy was unwritable.
Fixed the issue that the database proxy node was switched due to database instance errors in some scenarios.
1.3.5
2023-1
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Performance optimizations
Optimized the performance when a large number of read statements were executed concurrently.
1.3.4
2022-12
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue that the returned data of SHOW PROCESSLIST was incomplete.
1.3.3
2022-11
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue that an error may occur during statement precompilation under a session-level connection pool.
1.3.2
2022-10
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Fixes
Fixed the issue that an error may occur during statement precompilation.
1.3.1
2022-10
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
Allowed instances with a weight of 0 to sustain read requests when the weight of all valid instances under the database proxy is 0. 
Supported the multi-AZ deployment architecture where read-only instances can be mounted across AZs. 
Provided the read-only mode. 
Supported transaction split. 
Supported momentary disconnection prevention, i.e., connection persistence, where the client will not be disconnected when a database instance HA switch occurs because of a scheduled task.
1.2.1
2022-6
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
Supported the lower_case_table_names parameter. By default, the case is not verified.
1.1.3
2021-6
MySQL 5.7 20211030 and later
MySQL 8.0 20211202 and later
Feature updates
Supported using a hint that indicates the route information in precompiled MySQL statements. When a hint is used in a PREPARE statement to specify the route destination, subsequent EXECUTE messages will be sent to the specified backend node.
Fixes
Fixed the issue that the frontend connection was reset immediately after source-replica switch of the source instance on the database proxy was performed. 
Fixed the issue that load balancing might fail when read-only instances exceeded the latency threshold. Routing will resume normally when the read-only instance latency falls below the threshold. 
Fixed the issue that MySQL 8.0 might return incorrect handshake information and cause connection failures.
1.1.2
2021-6
MySQL 5.7 20211030 and later
MySQL 8.0 20211130 and later
Feature updates
Supported MySQL 8.0. 
Supported the connection pool feature at the connection level, which is useful in scenarios where non-persistent connections to the database are frequently established. The database proxy will save connections and reuse them during subsequent connection establishments. 
Supported the reconnection feature for read-only instances. In persistent connection scenarios, when a read-only instance is restarted or added, the database proxy will automatically establish a connection and restore routing to it. 
Updated the internal memory management mechanism to reduce the memory usage.
Fixes
Fixed the issue that the client connection persisted after the backend connection was closed due to timeout. 
Fixed the issue that the internal cache might cause excessively rapid increase of the memory utilization. 
Fixed the occasional issue that messages in an incorrect format were returned.
1.0.1
2022-2
MySQL 5.7 20201230 and later
Feature updates
Supported MySQL 5.7. 
Supported read/write separation. 
Supported read weight assignment in read/write separation. 
Supported the configuration of source-replica replication delay threshold. Routing to a read-only instance will be stopped if its delay exceeds the thresholds and will be recovered after it drops below the threshold. If the source-replica replication is interrupted, disconnected read-only instances will be removed directly. 
Supported the configuration of the least number of read-only instances. When read-only instances are removed, if the number is set to N, at least N instance(s) will be retained for routing. 
Supported the failover configuration, which is enabled by default. If it is disabled and the read weight of the source instance is 0, after all read-only instances are removed, an error will be reported for read requests. If failover is enabled and the read weight of the source instance is not 0, requests will be routed to the source instance. 
Supported using a hint to specify the destination node for routing.
Database Proxy Version
Release Date
MySQL Kernel Version Requirements
Description
1.4.5
2025-9
MySQL 5.7 20211230 and later
MySQL 8.0 20221215 and later
Read-only analysis engine 2.2410.4.0 and later
Feature update
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.
Bug fixes
Fixed the issue of memory leakage that occurred with a low probability in the transaction-level connection pool.
Fixed the issue of connection interruption that occasionally occurred during the primary database switch after the transaction-level connection pool is enabled.
1.4.4
2025-3
MySQL 5.7 20211230 and later
MySQL 8.0 20221215 and later
Read-only analysis engine 2.2410.4.0 and later
Feature updates
Supported participating in database proxy read-write separation and removal upon faults of LibraDB instances with the read-only analysis engine.
Supported using the hint /* to ap */ in SQL statements to route SQL statements to a read-only analysis engine instance.
1.4.2
2023-8
MySQL 5.7 20211230 and later
MySQL 8.0 20221215 and later
Fixes
Fixed the issue of excessive memory usage after the transaction-level connection pool is enabled.  
1.4.1
2023-7
MySQL 5.7 20211230 and later
MySQL 8.0 20221215 and later
Feature updates
Supports the transaction-level connection pool feature.
Fixes
Fixed the issue that DDL statements would get stuck in the secondary database.

Was this page helpful?

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

Yes

Feedback

Database Proxy Version	Release Date	MySQL Kernel Version Requirements	Description
1.3.20	2025-11	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Only the version was updated, and the supported capabilities were not changed.
1.3.19	2025-7	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Bug fixes Fixed the issue that the momentary disconnection prevention feature might cause incorrect connection character sets.
1.3.17	2025-5	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue where errors occasionally occurred during read-only transaction initiating after transaction splitting is enabled. Addressed the issue where character set errors may occur during connection reuse after the connection pool is enabled.
1.3.16	2025-3	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	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 the issue that the connection might be interrupted when the replication delay of a read-only instance changed frequently after delayed read-only instance removal was enabled.
1.3.15	2024-12	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Performance optimizations Optimized memory usage under high load conditions, addressing the issue of prolonged high memory utilization. Fixes Resolved the issue where the anti-disconnection feature occasionally failed.
1.3.14	2024-11	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates The statements SHOW BINLOG EVENTS and SHOW BINARY LOGS are now routed to the root instance. Optimized the issue that querying large messages may result in excessive memory consumption. Fixes Fixed the occasional inconsistency between the character set sorting of the handshake messages and the backend databases. Fixed the issue that the primary-secondary switch in the primary database may cause interruption in the read-only address connection. Fixed the issue of the potential authentication failure when a specified IP address matches multiple accounts simultaneously.
1.3.13	2024-8	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates System variables related to SELECT binlog will be sent to the primary database for execution. Added new high-availability detection statements to reduce the migration caused by false fault detections. Optimized the memory usage of the database proxy kernel in multi-threading scenarios. Fixes Fixed the issue that an error was reported when a precompiled statement was executed in a read-only transaction. Fixed the performance issue caused by frequent connection establishment 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	2024-6	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates The SHOW VARIABLES statement will be sent to the primary database for execution. Fixes Fixed the issue that a large number of connections triggering momentary disconnection prevention could cause some connections to be stuck for too long. Fixed the issue that a large number of connections triggering re-load balancing could cause some connections to fail to be broken as expected.
1.3.11	2024-5	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue that too many accounts could lead to connection failures. Note: Version 1.3.12 already includes this fix, so it is recommended to upgrade to 1.3.12 directly.
1.3.10	2024-3	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue that encountering specific messages during message processing could cause anomalies.
1.3.9	2024-1	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue that annotations in multi-statements caused incorrect parsing.
1.3.8	2023-9	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates Supports more functions updated in MySQL 5.7 and 8.0. Optimized the parser cache to reduce OOM probability under a large number of complex SQL statements. Added traffic monitoring metrics for the database proxy. Supports the dynamic CLB feature. Fixes Fixed the issue that the momentary disconnection prevention feature might fail for some connections under a high connection count.
1.3.7	2023-4	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	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, causing the system to mistakenly determine that the database proxy was unwritable. Fixed the issue that the database proxy node was switched due to database instance errors in some scenarios.
1.3.5	2023-1	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Performance optimizations Optimized the performance when a large number of read statements were executed concurrently.
1.3.4	2022-12	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue that the returned data of SHOW PROCESSLIST was incomplete.
1.3.3	2022-11	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue that an error may occur during statement precompilation under a session-level connection pool.
1.3.2	2022-10	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Fixes Fixed the issue that an error may occur during statement precompilation.
1.3.1	2022-10	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates Allowed instances with a weight of 0 to sustain read requests when the weight of all valid instances under the database proxy is 0. Supported the multi-AZ deployment architecture where read-only instances can be mounted across AZs. Provided the read-only mode. Supported transaction split. Supported momentary disconnection prevention, i.e., connection persistence, where the client will not be disconnected when a database instance HA switch occurs because of a scheduled task.
1.2.1	2022-6	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates Supported the lower_case_table_names parameter. By default, the case is not verified.
1.1.3	2021-6	MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later	Feature updates Supported using a hint that indicates the route information in precompiled MySQL statements. When a hint is used in a PREPARE statement to specify the route destination, subsequent EXECUTE messages will be sent to the specified backend node. Fixes Fixed the issue that the frontend connection was reset immediately after source-replica switch of the source instance on the database proxy was performed. Fixed the issue that load balancing might fail when read-only instances exceeded the latency threshold. Routing will resume normally when the read-only instance latency falls below the threshold. Fixed the issue that MySQL 8.0 might return incorrect handshake information and cause connection failures.
1.1.2	2021-6	MySQL 5.7 20211030 and later MySQL 8.0 20211130 and later	Feature updates Supported MySQL 8.0. Supported the connection pool feature at the connection level, which is useful in scenarios where non-persistent connections to the database are frequently established. The database proxy will save connections and reuse them during subsequent connection establishments. Supported the reconnection feature for read-only instances. In persistent connection scenarios, when a read-only instance is restarted or added, the database proxy will automatically establish a connection and restore routing to it. Updated the internal memory management mechanism to reduce the memory usage. Fixes Fixed the issue that the client connection persisted after the backend connection was closed due to timeout. Fixed the issue that the internal cache might cause excessively rapid increase of the memory utilization. Fixed the occasional issue that messages in an incorrect format were returned.
1.0.1	2022-2	MySQL 5.7 20201230 and later	Feature updates Supported MySQL 5.7. Supported read/write separation. Supported read weight assignment in read/write separation. Supported the configuration of source-replica replication delay threshold. Routing to a read-only instance will be stopped if its delay exceeds the thresholds and will be recovered after it drops below the threshold. If the source-replica replication is interrupted, disconnected read-only instances will be removed directly. Supported the configuration of the least number of read-only instances. When read-only instances are removed, if the number is set to N, at least N instance(s) will be retained for routing. Supported the failover configuration, which is enabled by default. If it is disabled and the read weight of the source instance is 0, after all read-only instances are removed, an error will be reported for read requests. If failover is enabled and the read weight of the source instance is not 0, requests will be routed to the source instance. Supported using a hint to specify the destination node for routing.

tencent cloud