Update the minor engine version of an ApsaraDB RDS for PostgreSQL instance - ApsaraDB RDS

ApsaraDB RDS for PostgreSQL allows you to update the minor engine version of an ApsaraDB RDS for PostgreSQL instance. You can update the minor engine version of your RDS instance to improve instance performance, use new features, and fix bugs. This helps ensure continuous optimization and security of your RDS instance.

For more information about the features of AliPG, see Release notes for AliPG.

Usage notes

When you update the minor engine version of your RDS instance, a transient connection that lasts approximately 30 seconds may occur. We recommend that you update the minor engine version during off-peak hours or make sure that your application is configured to automatically reconnect to the RDS instance.
After you update the minor engine version of your RDS instance, you cannot roll the minor engine version of the RDS instance back to the previous version.
In most cases, minor engine version updates do not cause compatibility issues. However, extension updates may cause compatibility issues. If an extension such as an extension of GanosBase needs to be updated when you update the minor engine version of your RDS instance, we recommend that you migrate the data of the RDS instance to a new RDS instance and then use the new RDS instance to test the compatibility of the updated extension with your workloads. For more information, see Restore data of an ApsaraDB RDS for PostgreSQL instance.
When you update extensions, take note of the following items:
- If the PostGIS extensions or extensions of GanosBase are used, you must manually update the extensions after the minor engine version of your RDS instance is updated. For more information, see How do I update the extensions of GanosBase?
- If your RDS instance runs PostgreSQL 14 with a minor engine version of earlier than 20230330 and uses the TimescaleDB extension of version 2.5.0 or earlier, you must execute the ALTER EXTENSION timescaledb UPDATE; statement to manually update the extension after you update the minor engine version to 20230330 or later. This way, the extension can run as expected.

View the minor engine version of an RDS instance

You can use one of the following two methods to view the minor engine version of your RDS instance:

Log on to the ApsaraDB RDS console and go to the Basic Information page of the RDS instance.
Note
This method is supported only for RDS instances that use cloud disks.
Connect to the RDS instance and run the show rds_release_date; command. For more information, see Connect to an ApsaraDB RDS for PostgreSQL instance.
Note
This method is supported for RDS instances that use local disks and cloud disks.

Manually update the minor engine version

Manually update the minor engine version of an RDS instance that uses local disks

If your RDS instance uses local disks, you cannot manually update the minor engine version of the RDS instance. You can restart your RDS instance. During the restart process, the system automatically updates the minor engine version of your RDS instance to the latest version. For more information, see Restart an ApsaraDB RDS for PostgreSQL instance.

Note

If your RDS instance is a primary RDS instance and is attached with read-only RDS instances, you must restart all the read-only RDS instances one by one before you restart the primary RDS instance. If you restart only the primary RDS instance, the system does not update the minor engine versions of the read-only RDS instances.

Manually update the minor engine version of an RDS instance that uses cloud disks

Note

If your RDS instance is a primary RDS instance and is attached with read-only RDS instances, you can use one of the following methods to update the minor engine versions of the RDS instances:

Update the minor engine version of the primary RDS instance. If you use this method, the system immediately updates the minor engine versions of the read-only RDS instances that are attached to the primary RDS instance and then the minor engine version of the primary RDS instance.
Update the minor engine versions of the read-only RDS instances one by one. Then, update the minor engine version of the primary RDS instance. This method is suitable if you do not want to update the minor engine versions of all read-only instances at once.

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 Configuration Information section, click Update Minor Engine Version.
In the dialog box that appears, configure the Latest Version and Update Time parameters and click OK.
The following list describes the fields in the value of the Latest Version parameter:
- rds: the RDS instance.
- postgres: the PostgreSQL database.
- 1200: the major version of PostgreSQL, which is 12 in this example.
- 20220830: the version of AliPG. For more information, see Release notes for AliPG.
- 12.11: the minor version of PostgreSQL, which is 12.11 in this example.

Automatically update the minor engine version

Note

This method is supported only for RDS instances that use cloud disks.

When you purchase an RDS instance that uses cloud disks, the Minor Engine Version Update Policy parameter is automatically set to Automatic Upgrade. If the minor engine version of your RDS instance is outdated, the system automatically delivers O&M tasks to update the minor engine version from time to time. The system notifies you of the tasks by email or internal message. For more information, see Set the maintenance window of an ApsaraDB RDS for MySQL instance. You can change the update time on the Event Management page or cancel the update task before it starts. For more information, see Scheduled events.

image..png

Modify automatic update settings

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 Configuration Information section of the Basic Information page, view the settings of automatic minor engine version update.Automated Update of Minor Engine Version
Click Settings to the right of Automated Update of Minor Engine Version.
In the dialog box that appears, select Automatic Upgrade or Manual Upgrade and click .

FAQ

An error occurs when I use the PostGIS extensions or extensions of GanosBase after I update the minor engine version of my RDS instance. What do I do?

After you update the minor engine version of your RDS instance, you must manually update the PostGIS extensions or extensions of GanosBase. For more information, see How do I update the extensions of GanosBase?

What are the compatibility issues caused by the PostGIS extensions during the minor engine version update?

The following table describes the differences.

Note

If your RDS instance runs a minor engine version earlier than 20211031, the following compatibility issues may occur.

Version of the PostGIS extensions

Update only of the minor engine version

Update of the minor engine version and the PostGIS extensions

2.5.x

If you use the following functions, your database may break down:
- ST_ClusterKMeans
- ST_GeomFromKML
- ST_AsKML
If you use the following functions, errors are reported:
- ST_Buffer
  Error: Invalid buffer parameter: uad_segs (accept: 'endcap', 'join', 'mitre_limit', 'miter_limit', 'quad_segs' and 'side')
  Solution: Change the quadsegs parameter to quad_segs.
- ST_Intersects
  Error: ERROR: GetGenericCacheCollection: Could not find upper context
  Solution: none.
The following functions are deleted and cannot be used:
- ST_Force_2D
- ST_Locate_Along_Measure
- ST_Estimated_Extent
The values or configuration methods of the following functions may change after the update:
- ST_GeomFromGeoJSON: The SRID=4326 setting is specified by default after the upgrade.
- ST_AsGeoJSON: The value of the maxdecimaldigits parameter is changed from 16 to 9.
- The configuration methods of MutliPoint change:
  - Before the update: MULTIPOINT(1 1,-1 1)
  - After the update: MULTIPOINT((1 1),(-1 1))

The following functions are deleted and cannot be used:
- ST_Force_2D
- ST_Locate_Along_Measure
- ST_Estimated_Extent
The values or configuration methods of the following functions may change after the update:
- ST_GeomFromGeoJSON: The SRID=4326 setting is specified by default after the upgrade.
- ST_AsGeoJSON: The value of the maxdecimaldigits parameter is changed from 16 to 9.
- The configuration methods of MutliPoint change:
  - Before the update: MULTIPOINT(1 1,-1 1)
  - After the update: MULTIPOINT((1 1),(-1 1))

3.1.x

If you use the following functions, your database may break down:
- ST_ClusterKMeans
The configuration methods of MutliPoint change:
- Before the update: MULTIPOINT(1 1,-1 1)
- After the update: MULTIPOINT((1 1),(-1 1))

The configuration methods of MutliPoint change:

Before the update: MULTIPOINT(1 1,-1 1)
After the update: MULTIPOINT((1 1),(-1 1))

Reference

If you already use the PostGIS or GanosBase extension in your business, you must manually upgrade the extension after you update the minor engine version of the instance. For more information about how to upgrade the extension, see Update the extensions of Ganos.
For more information about minor engine versions, see Release notes for AliPG.

You can also call the operations described in the following table to update the minor engine version of your instance.

Operation	Description
UpgradeDBInstanceKernelVersion	Updates the minor engine version of an instance.
ModifyDBInstanceAutoUpgradeMinorVersion	Changes the method that is used to update the minor engine version of an instance.