tencent cloud

Feedback

Kernel Minor Version Release Notes

Last updated: 2023-02-07 11:53:30
    This document describes the release notes of the TDSQL-C for MySQL database proxy.

    Viewing database proxy version

    On the cluster list page, proceed according to the actually used view mode:
    Tab view
    List view
    Option 1 On the cluster management page, click Database Proxy and view it in Overview > Basic Info > Proxy Version.
    
    Option 2 On the Cluster Details tab on the cluster management page, click Details after Database Proxy in the architecture to enter the Database Proxy page, and view it in Overview > Basic Info > Proxy Version.
    
    You can view the version in Overview > Proxy Version on the Database Proxy tab.
    

    Version description

    Note:
    If the TDSQL-C for MySQL kernel version requirements are not met, you can upgrade the kernel version of your database first as instructed in Upgrading Kernel Minor Version.
    Version
    TDSQL-C for MySQL Kernel Version Requirement
    Description
    1.3.3
    TDSQL-C for MySQL 5.7 ≥ 2.0.20/2.1.6TDSQL-C for MySQL 8.0 ≥ 3.1.6
    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 didn't have a parameter type.
    1.2.1
    -
    Feature updates
    Supported MySQL 5.7/8.0.
    Supported cluster deployment to deploy multiple instances under one database proxy.
    Supported read/write separation and corresponding weight configuration.
    Supported the failover feature to send read requests to the read-write instance in case of read-only instance failures.
    Supported the load balancing feature to balance the connections to each proxy node.
    Supported using the HINT syntax to specify router nodes.
    Supported the session-level connection pool for scenarios where non-persistent connections were frequently established to the database.
    Allowed the database proxy to save connections and reuse them subsequently.
    Supported hot loading to modify configurations online without restarting the dedicated database proxy.
    Supported the reconnection feature for read-only instances. In persistent connection scenarios, when a read-only instance was restarted or added, the database proxy would automatically establish a connection and restore routing to it.
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support