This topic describes how to change the specifications of an ApsaraDB RDS for PostgreSQL instance. The specifications include the RDS edition, instance type, and storage capacity.
Your Alibaba Cloud account does not have unpaid renewal orders.
You can create read-only RDS instances to offload read requests from the primary RDS instance in your database system. This way, the read capability of your database system is increased. For more information, see Overview of read-only ApsaraDB RDS for PostgreSQL instances and Create a read-only ApsaraDB RDS for PostgreSQL instance.
|Edition||You can upgrade an RDS instance from RDS Basic Edition to RDS High-availability Edition. For more information, see Upgrade an ApsaraDB RDS for PostgreSQL instance from Basic Edition to High-availability Edition.||A transient connection that lasts a few seconds occurs.|
Note Storage performance varies based on the storage type and the performance level (PL) in ascending order: standard SSDs, ESSDs of PL1, ESSDs of PL2, and ESSDs of PL3.
|Instance type||You can change the instance type of your RDS instance regardless of the instance configuration.
Notice If your RDS instance uses a new general-purpose instance type, you can change the instance type of your RDS instance only to a different new general-purpose instance type. For more information, see Primary ApsaraDB RDS for PostgreSQL instance types.
|A transient connection that lasts a few seconds occurs.|
|Storage capacity||You can increase the storage capacity of your RDS instance regardless of the instance
For more information, see Specification change fees.
- If your RDS instance runs RDS Basic Edition, no secondary RDS instance is provided
as 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 the specifications of your RDS instance, ApsaraDB RDS may migrate the data of your original 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 specified switching time. During the switchover, a transient connection that lasts up to 30 seconds occurs. The duration of the transient connection varies based on the different configuration items. And 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 during off-peak hours, or make sure that your application is configured to automatically reconnect to your RDS instance. For more information about the impacts of different configuration items, see the Impact column of the Configuration items.
- 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.
- Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
- In the Configuration Information section of the Basic Information page, click Change Specifications.
- 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 You can select one of the following specification change methods:
Upgrade or Downgrade
After you submit a specification change order, the new specifications immediately take effect. Both specification change methods are supported for subscription RDS instances and pay-as-you-go RDS instances.
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 ID and endpoints, about the RDS instance over to the new RDS instance based on the specification change method that you select.
- Change the specifications of the RDS instance. For information, see Configuration items.
- 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 is complete.
- Switch Within Maintenance Window: When the specification change is being applied, a transient connection that lasts approximately 30 seconds 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.
- 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.
- How do I change the storage type of my RDS instance from standard SSDs or ESSDs to
For more information, see How do I migrate an ApsaraDB RDS instance from standard or enhanced SSDs to local SSDs?.
- If I only increase 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.
|ModifyDBInstanceSpec||Changes the specifications of an ApsaraDB RDS instance.|