Upgrade an ApsaraDB RDS for PostgreSQL instance from Basic Edition or High-availability Edition to Cluster Edition

Background information

RDS Cluster Edition for ApsaraDB RDS for PostgreSQL uses an HA architecture that contains one primary node and multiple secondary nodes and supports compute-storage separation. RDS Cluster Edition provides the following features: automated failover, primary/secondary switchover, readable secondary nodes, node addition and deletion, multi-zone disaster recovery, node-level monitoring, and cluster topology management. For more information, see RDS Cluster Edition.

Prerequisites

• The RDS instance runs PostgreSQL 14 or later.

• The RDS instance runs RDS Basic Edition or RDS High-availability Edition.

  Note

  You can view the instance family on the Basic Information page.

• The instance uses the enterprise SSD (ESSD) or Premium ESSD storage type.

  Note

  • Instances that use premium performance disks do not support the I/O acceleration or data archiving feature.

  • If the instance uses a standard SSD, you must first upgrade it to an enterprise SSD (ESSD). For more information, see Upgrade a standard SSD to an ESSD.

• The RDS instance is a primary RDS instance and does not have read-only RDS instances.

• The database proxy feature is disabled for the RDS instance.

• Babelfish is disabled for the RDS instance. If the suffix of the minor engine version of the RDS instance does not include babelfish, Babelfish is disabled.

• PgBouncer is disabled for the RDS instance.

Billing rules

For more information, see Specification changes.

Impacts

• The upgrade can trigger a data migration, which may require a few minutes. After the migration is complete, a switchover of your workloads is triggered at the switching time that you specify. During the switchover, a transient connection lasts approximately 30 seconds. Make sure that your application is configured to automatically reconnect to your RDS instance.

  Note

  After the upgrade, the endpoint of the RDS instance remains unchanged. You do not need to modify application configurations.

• After the upgrade, you cannot downgrade the RDS edition of your RDS instance to RDS Basic Edition or RDS High-availability Edition.

Procedure

1. Log on to the ApsaraDB RDS console and 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 instance ID.

2. In the Configure Information section of the Basic Information page, click Change Specifications.

3. In the dialog box that appears, select Upgrade and click Next step. This step is required only for subscription RDS instances.

4. Configure the following parameters.

   Parameter name	Description
   Product Family	Select Cluster Edition.
   Storage Type	Select the storage type that you want to use. For more information, see Storage types.
   Instance Type	Select an instance type that you want to use. Select the instance type. Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary ApsaraDB RDS instance types.
   Storage Capacity	Specify the storage capacity of your RDS instance. The storage capacity can only be increased but cannot be decreased.
   Switching Time	Specify the time to perform the workload switchover. Valid values: Execute Immediately: The data is immediately migrated, which does not affect the workloads on the RDS instance. After the data is migrated, your workloads are immediately switched over. Switch Within Maintenance Window: The data is immediately migrated, which does not affect the workloads on the RDS instance. After the data is migrated, your workloads are switched over within the specified maintenance window.

5. Carefully review the Upgrade/Downgrade Reminder to confirm that the information is correct, select the Terms of Service checkbox, and click Proceed To Payment.

6. In the dialog box that appears, confirm the instance information before and after the specification change and click Continue to complete the payment.

7. Check whether the upgrade is successful: On the Basic Information page, check the value of the Type and Edition parameter. If the value is Regular Instance (Cluster Edition), the upgrade is successful.

Related APIs