Release notes for database proxy versions of an ApsaraDB RDS for PostgreSQL instance - ApsaraDB RDS

ApsaraDB RDS for PostgreSQL upgrades the database proxy version at irregular intervals. This topic describes the release notes for the database proxy version of ApsaraDB RDS for PostgreSQL. This helps you understand the new features, optimizations, and bug fixing of each database proxy version.

View the database proxy version of an RDS instance

Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the left-side navigation pane, click Database Proxy.
In the Basic Information section, check the value of Proxy Version.
If Upgrade is displayed to the right of the database proxy version, click Upgrade to view the latest database proxy version and perform the upgrade based on your business requirements.
Note
- For more information about how to upgrade the database proxy version of an RDS instance, see Upgrade the database proxy version of an ApsaraDB RDS for MySQL instance.
- You can also call an API operation to view the database proxy version. For more information, see DescribeDBProxy.

Release notes for the database proxy version

Note

The following table contains only the mainstream database proxy versions rather than all database proxy versions. The database proxy version that you use may not be included in the list.

Database proxy version	Description
1.13.12_20231219	New features: Data replication between RDS instances can be implemented by using database proxy endpoints. Bug fixes: The bug that data migration across different RDS instances stops unexpectedly is fixed.
1.13.12_20230621	New features: The database proxy feature is released for ApsaraDB RDS for PostgreSQL for the first time. The read/write and read-only attributes are supported for database proxies. Bug fixes: The bug that an authentication failure occurs when you connect to a database proxy endpoint is fixed. The bug that an out of memory (OOM) error occurs when the Authorization field is contained in an HTTP request is fixed.