Change the specifications of an ApsaraDB RDS for PostgreSQL instance

Configuration items

You can create read-only RDS instances to increase the read capability of your database system. The read-only RDS instances can offload queries from the primary RDS instance. For more information, see Overview of read-only ApsaraDB RDS for PostgreSQL instances and Create a read-only ApsaraDB RDS for PostgreSQL instance.

Billing

For more information, see Specification change fees.

Precautions

• If your RDS instance runs RDS Basic Edition, no secondary RDS instance is provided as a hot standby. In this case, if your RDS instance unexpectedly exits, your database service may be unavailable for a long period of time. If you change the specifications or upgrade the database engine version of your RDS instance, your database service may also be unavailable for a long period of time. If you have high requirements for service availability, we recommend that you do not use RDS Basic Edition.
  Note Whether a transient connection occurs during the specification changes varies based on the different configuration items. For more information, see the Impact column of the Configuration items.
• When you change some specifications of your RDS instance, ApsaraDB RDS may migrate the data of your RDS instance to a new RDS instance. After the migration is complete, ApsaraDB RDS switches your workloads over to the new RDS instance. During the switchover, a transient connection or instance restart may occur. You cannot perform most of the operations that are related to databases, accounts, and network settings during the switchover. We recommend that you change the specifications of your RDS instance within the specified maintenance window. For more information, see Set the maintenance window of an ApsaraDB RDS for PostgreSQL instance. For more information about the impacts of different configuration items, see the Impact column.
• After you change the specifications of your RDS instance, the ID and endpoints of the instance remain unchanged.
• After you change the specifications of your RDS instance, you do not need to manually restart the instance.

Procedure

1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
2. In the Configuration Information section of the Basic Information page, click Change Specifications.
3. In the dialog box that appears, select a specification change method and click Next step. This step is required only when the RDS instance uses the subscription billing method.
   Note Upgrade or Downgrade:

   • After you submit a specification change order, ApsaraDB RDS synchronizes the data of the RDS instance from the disk to a new RDS instance. Then, ApsaraDB RDS switches the information, such as the instance ID and endpoints, about the RDS instance over to the new RDS instance based on the specified switching time.
   • If you select Downgrade, the primary RDS instance is restarted during the switchover. We recommend that you change the specifications of the RDS instance within the specified maintenance window. For more information, see Set the maintenance window of an ApsaraDB RDS for PostgreSQL instance
4. Change the specifications of the RDS instance. For more information about the supported configuration items, see Configuration items.
5. Configure the Switching Time parameter.
   • Switch Immediately After Data Migration: The specification change triggers a data migration to a new RDS instance. If you select this option, ApsaraDB RDS immediately applies the specification change and switches your workloads over to the new RDS instance after the migration process is complete.
   • Switch Within Maintenance Window: When the specification change is being applied, a transient connection or instance restart may occur and you cannot perform most of the operations that are related to databases, accounts, and network settings. If you select this option, ApsaraDB RDS applies the specification change during the maintenance window that you specify. For more information, see Set the maintenance window of an ApsaraDB RDS for PostgreSQL instance.

   Note If you only increase the storage capacity of the RDS instance or only change the ESSD storage type of the RDS instance between ESSDs PL1, ESSDs PL2, and ESSDs PL3, your business is not affected. ApsaraDB RDS immediately applies the specification change. In this case, you do not need to select Switch Within Maintenance Window.
6. Read and select Terms of Service, click Pay Now, and then complete the payment.
   Warning

   • After you submit a specification change order, you cannot cancel the order. Therefore, before you submit a specification change order, we recommend that you evaluate whether the new specifications meet your business requirements.
   • After you submit a specification change order, do not perform DDL operations before the specification change is applied.

FAQ

1. How do I change the storage type of my RDS instance from standard SSDs or ESSDs to local SSDs?

   For more information, see How do I migrate an ApsaraDB RDS instance from standard or enhanced SSDs to local SSDs?.

2. If I increase only the storage capacity of my RDS instance, does ApsaraDB RDS migrate the data of my original RDS instance to a new RDS instance?

   This depends on whether the host on which your RDS instance resides has sufficient storage. If the host has sufficient storage, no data migration is required. Otherwise, ApsaraDB RDS migrates the data to a host that has sufficient storage.

3. How do I decrease the storage space of my RDS instance?
   You cannot decrease the storage capacity of your RDS instance by changing the specifications of the instance.

   • If your RDS instance uses local SSDs, we recommend that you use the major version upgrade feature to upgrade the instance to an instance that runs PostgreSQL 11 or later and uses standard SSDs or ESSDs. You can decrease the storage capacity when you upgrade the instance. For more information, see Upgrade the major engine version of an ApsaraDB RDS for PostgreSQL instance.
   • If your RDS instance uses standard SSDs or ESSDs and does not use a new general-purpose instance type, we recommend that you use the cloud migration feature to reduce the storage capacity. For more information, see Primary ApsaraDB RDS for PostgreSQL instance types and Scale down an ApsaraDB RDS for PostgreSQL instance.

Related operations