This topic describes the release notes for dedicated proxy versions.

Note

View the dedicated proxy version of an RDS instance

If the RDS instance is not using the latest dedicated proxy version, click Upgrade Dedicated Proxy Version on the Database Proxy page of the RDS instance in the ApsaraDB RDS console. In the dialog box that appears, check the in-use dedicated proxy version (Current Version) and the available dedicated proxy version (Available Upgrade).

Note If the RDS instance is using the latest dedicated proxy version, the Upgrade Dedicated Proxy Version button is not displayed. Users can also view the dedicated proxy version of the RDS instance by calling an API operation. For more information, see Query dedicated proxy details.
View the dedicated proxy version of an RDS instance

Updates to dedicated proxy versions

The following table contains only the mainstream dedicated proxy versions rather than all dedicated proxy versions.

Dedicated proxy version Description
1.13.25 Bug fixes:
  • The bug that causes memory leaks in the dedicated proxy of an RDS instance due to authentication failures is fixed.
  • The bug that causes the dedicated proxy of an RDS instance to unexpectedly exit is fixed. This bug is triggered if an application connects to the dedicated proxy by using multiple endpoints.
1.13.22
  • New features:
    • The SELECT LAST_INSERT_ID() statement can be executed after the INSERT statement to obtain the unique ID of a sharded table.
    • The FOUND_ROWS function is supported.
    • The requests for running the COM_STATISTICS command can be routed to read-only RDS instances.
    • The optimized transaction connection pool feature is supported.
    • The requests for invoking the GEO function can be routed to read-only RDS instances.
    • A few internal metrics are added to monitor the performance of RDS instances.
  • Bug fixes:
    • The bug that causes requests to be routed to locked RDS instances is fixed.
    • The bug that causes routing errors due to the incorrect parsing of some statements is fixed.
    • The bug that causes failures in running the stmt_exec command is fixed.
    • The bug that causes failures in executing the LOAD DATA INFILE statement is fixed.
1.13.17 Bug fixes:

A few internal bugs are fixed.

1.13.5
  • New features:
    • The Force Node Connection feature is provided to route all requests to a specified node. For example, the /*force_proxy_internal*/set force_node = 'pi-123'; setting specifies that all requests over a specifiied connection are routed to the pi-123 node.
      Note If the specified node is faulty, the "set force node 'pi-123' is not found, please check." error is returned.
    • The Force Node Query feature is provided to route a specified request to a specified node. For example, the /*force_node='pi-123'*/ show processlist; setting specifies that a specified request is routed to the pi-123 node.
      Note If the specified node is faulty, the "'force hint server node is not found, please check'." error is returned.
    • A few internal metrics are added to monitor the performance of RDS instances.
  • Bug fixes:
    • The bug that causes requests to be routed to read-only RDS instances is fixed. This bug is triggered if the statements in the requests contain the MODE keyword.
    • The bug that causes unbalanced loads is fixed.
1.12.10
  • New features:

    SSL encryption can be enabled for dedicated proxy endpoints.

  • Bug fixes:
    • The bug that causes exceptions in establishing SSL connections to an RDS instance is fixed. This bug is triggered if the RDS instance runs MySQL 8.0.
    • The bug that prevents the enabled dedicated proxies from properly routing new requests to an RDS instance is fixed. This bug is triggered if the RDS instance is restored from an abnormal state to a normal state.
1.12.7
  • New features:
    • The SHOW FULL PROCESSLIST statement is supported.
    • The syntax for XA transactions is supported.
  • Bug fixes:
    • The bug that causes errors in executing the SHOW PROCESSLIST statement on an RDS instance is fixed. This bug is triggered if the RDS instance runs MySQL 8.0.
    • A few bugs that affect the transaction connection pool feature are fixed.
    • A few bugs that cause connection failures are fixed.
1.11.12
  • New features:

    The transaction connection pool feature is supported. For more information, see Set the connection pool type of an ApsaraDB RDS for MySQL instance.

  • Bug fixes:
    • The bug that prevents new requests over the previous persistent connections to an RDS instance from being routed to the RDS instance is fixed. This bug is triggered if the RDS instance is restored from an abnormal state to a normal state. This bug is fixed by optimizing the mechanism that is used to balance loads among persistent connections.
    • The bug that prevents the PREPARE statement from being sent in unicast mode is fixed by optimizing the syntax of the PREPARE statement.
    • The bug that causes failures in connecting MySQL 5.7 databases to MySQL 5.6 databases is fixed. This bug is triggered if the Deprecate EOF feature is enabled.
    • The bug that causes disconnections to an RDS instance is fixed. This bug is triggered if stored procedures are invoked to modify the RDS instance.
    • The bug that causes a client to report the Packets out of order error is fixed. This bug is triggered if the size per line of large packets in a result set exceeds 16 MB.
    • The bug that prevents the timely termination of transactions on a read-only RDS instance is fixed. This bug is triggered if the transactions are started by the SET autocommit=0 statement.
    • The bug that causes a statement to be routed to a read-only RDS instance is fixed. This bug is triggered if LOCK IN SHARE MODE is specified in the statement.
    • The bug that causes the SELECT handler FROM abc statement to be routed to a read-only RDS instance is fixed. This bug is triggered if FOR UPDATE is specified in the statement.
    • The bug that causes failures in authenticating a user from more than one host is fixed.
1.10.7

Bug fixes:

A few bugs that affect the session connection pool feature are fixed.

1.9.23
  • New features:
    • The root account is granted the permissions to establish connections.
    • SSL connections are supported.
  • Bug fixes:
    • The bug that causes failures in running the change user command is fixed.
    • The bug that causes failures in running the load file command is fixed.
    • The bug that causes a client to report the "Exception: Packets out of order" error is fixed. This bug is triggered if the client receives packets that are in an unexpected sequence.
    • The bug that causes a read-only RDS instance to disconnect when its primary RDS instance becomes abnormal is fixed.
1.9.14
  • New features:

    The /*FORCE_SLAVE*/ and /*FORCE_MASTE*/ hints are supported.

  • Bug fixes:
    • The bug that causes the system to return garbled characters is fixed. This bug is triggered if the value of the charset parameter is invalid.
    • The bug that causes the system to return an invalid string for the MySQL version is fixed.