Configuration item | Description | Impact |
RDS 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 occurs. |
Product type | You can change the product type of your RDS instance between YiTian and standard. For more information about the differences between YiTian and standard instances, see Product types. Note If you cannot select the required product type when you change the specifications of the RDS instance, no resources are available in the zone in which the RDS instance resides. You can go to the ApsaraDB RDS buy page to view the zones that support the required product type, migrate the RDS instance to a zone that can provide the required resources, and then change the product type. For more information, see Migrate an ApsaraDB RDS for PostgreSQL instance across zones in the same region. If you want to change the product type of an RDS instance, make sure that the minor engine version of the RDS instance after the change is later than or the same as the current minor engine version. If the minor engine version after the change is earlier than the current minor engine version, the product type change fails. YiTian RDS instances do not support the plv8 and rdkit extensions. When you change the product type from standard to YiTian, make sure that these extensions are not used. For more information about the extensions supported by each product type, see Extensions supported by ApsaraDB RDS for PostgreSQL.
| A transient connection occurs. |
Storage type | You can change the storage type of your RDS instance. If your RDS instance uses cloud disks, take note of the following points: You can upgrade the storage type of your RDS instance from standard SSD to Enterprise SSD (ESSD). ESSDs support the following performance levels (PLs): PL1, PL2, and PL3. You cannot downgrade the storage type of your RDS instance from ESSD to standard SSD. You can upgrade or downgrade the ESSD storage type of your RDS instance between ESSD PL1, ESSD PL2, and ESSD PL3. You can change the storage type from ESSD to general ESSD but cannot from general ESSD to ESSD.
If your RDS instance uses local SSDs, you cannot change the storage type of the RDS instance.
Note For more information about the performance differences among different storage types, see Storage types. | If you upgrade or downgrade the ESSD storage type of your RDS instance between ESSD PL1, ESSD PL2, and ESSD PL3, your business running on the instance is not interrupted. If you change the storage type from ESSD to general ESSD, your business running on the instance is not interrupted. If you upgrade the storage type of your RDS instance from standard SSD to ESSD, your business running on the instance is transiently interrupted.
|
Instance type | You can change the instance type of your RDS instance. | If you upgrade the instance type of your RDS instance, a transient connection occurs. If you downgrade the instance type of your RDS instance, the primary RDS instance is restarted. After the primary RDS instance is restarted, a transient connection occurs. When you change the instance type of your RDS instance, make sure that specific kernel parameters of the read-only RDS instance are consistent with those of the primary RDS instance. If you change the kernel parameters of the read-only RDS instance, the read-only RDS instance is restarted and a transient connection occurs.
|
Storage capacity | You can expand or reduce the storage capacity of your RDS instance. Storage capacity expansion: You can expand the storage capacity of your RDS instance at a step size of 5 GB. The new storage capacity of your RDS instance cannot exceed the maximum storage capacity that is supported by the instance type of the RDS instance. For more information, see Primary ApsaraDB RDS instance types. Storage capacity reduction: You can reduce the storage capacity of your RDS instance that uses cloud disks without the need to change the RDS edition or architecture of the RDS instance. The new storage capacity of your RDS instance must be greater than or equal to the minimum storage capacity that is supported by the instance type of the RDS instance. You can use the following formula to calculate the minimum storage capacity to which you can reduce your RDS instance: min{Used storage × 1.3, Used storage + 400 GB}. You can reduce the storage capacity at a step size of 5 GB. For more information, see Reduce the storage capacity of an ApsaraDB RDS for PostgreSQL instance that uses cloud disks.
Your RDS instance uses a PL1 ESSD that provides 2,000 GB of storage capacity. The minimum storage capacity that is supported by the instance type of the RDS instance is 20 GB. If 10 GB of storage is used, the value calculated by using the preceding formula is 13 GB. In this case, the minimum storage capacity to which you can reduce your RDS instance is 20 GB. If 500 GB of storage is used, the value calculated by using the preceding formula is 650 GB. In this case, the minimum storage capacity to which you can reduce your RDS instance is 650 GB. If 1,500 GB of storage is used, the value calculated by using the preceding formula is 1,900 GB. In this case, the minimum storage capacity to which you can reduce your RDS instance is 1,900 GB.
Note If your RDS instance uses local disks, we recommend that you use the major version upgrade feature to upgrade the RDS instance to an instance that runs a later database engine version and uses cloud disks. You can reduce the storage capacity of your RDS instance when you upgrade the major engine version. For more information, see Upgrade the major engine version. If your RDS instance is created before October 10, 2022 and uses an original architecture, you must update the minor engine version to the latest version and then reduce the storage capacity of the RDS instance. For more information, see Update the minor engine version. You can manually change the specifications of your RDS instance that uses cloud disks to adjust the storage capacity. You can also enable the automatic storage expansion feature for your RDS instance. After the feature is enabled, the system automatically expands the storage capacity to ensure stable service operations when the percentage of the remaining storage reaches the specified threshold. For more information, see Configure automatic storage expansion for an ApsaraDB RDS for PostgreSQL instance. If the RDS instance is being backed up, you can start a storage capacity expansion task after the backup is complete. We recommend that you expand the storage capacity of the RDS instance at the point in time other than the backup time.
| If the primary RDS instance uses cloud disks, take note of the following points: If your RDS instance uses local disks, a transient connection occurs.
|
Elastic Compute Service (ECS)
Lingma
