All Products
Search
Document Center

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

Last Updated:Mar 30, 2026

RDS Basic Edition runs on a single node and has no redundancy. Upgrading to High-availability Edition adds a secondary instance in a primary/secondary architecture, reducing the risk of data loss and unplanned downtime.

Warning

This upgrade is irreversible. After the upgrade is complete, you cannot downgrade the instance back to RDS Basic Edition.

Prerequisites

Before you begin, make sure that:

  • The instance runs PostgreSQL 10 or later.

  • The instance family is Basic Series. To verify, check the Basic Information page of your instance.

Background information

High-availability Edition is a widely used edition suitable for more than 80% of use cases in various industries, such as Internet, IoT, online retail, logistics, and gaming. For more information, see RDS High-availability Edition.

How it works

When you upgrade from Basic Edition to High-availability Edition, RDS performs the following actions:

  1. Migrates data from the single-node instance. This process may take a few minutes.

  2. Creates a secondary instance and establishes a primary/secondary replication architecture between the primary and secondary instances.

  3. Triggers a workload switchover at the switching time you specify.

Billing

For a detailed cost breakdown, see Specification changes.

Upgrade to High-availability Edition

  1. Go to the Instances page. In the top navigation bar, select the region where your instance resides. Find the instance and click its ID.

  2. On the Basic Information page, go to the Configuration Information section and click Change Specifications.

  3. For subscription instances, select Upgrade and click Next in the dialog box.

  4. Configure the following parameters:

    Parameter Description
    Edition Select High-availability Edition.
    Storage type Select a storage type. This parameter is available only when the original instance uses ESSD. For details, see Storage types.
    Instance type Select an instance type. Each type defines the number of CPU cores, memory capacity, maximum connections, and maximum IOPS. For details, see Primary ApsaraDB RDS instance types.
    Storage capacity Set the storage capacity. Capacity can only be increased, not decreased.
    Switching time Choose when the workload switchover occurs: Execute Immediately or Switch Within Maintenance Window.
  5. Read the Terms of Service, click Confirm Order, and complete the payment.

After the upgrade: A transient connection interruption lasting approximately 30 seconds occurs during the workload switchover. Make sure your application is configured to automatically reconnect to the RDS instance.

API reference

API Description
Change the specifications of an instance Changes the specifications of an ApsaraDB RDS instance.