Some ApsaraDB RDS for PostgreSQL instance types are no longer available for sale from April 29, 2022 due to product optimization and resource planning adjustment.
Effective date
April 29, 2022
End-of-sale instance types
- pg.n2.medium.2c
- pg.n2.small.2c
- rds.pg.s1.small
Impacts and suggestions
Impacts
- When you purchase an ApsaraDB RDS for PostgreSQL instance, you can no longer select an end-of-sale instance type.
- You can continue to use existing ApsaraDB RDS for PostgreSQL instances that use end-of-sale instance types. However, you cannot select an end-of-sale instance type in specific scenarios. For example, you cannot select an end-of-sale instance type when you restore the data of an ApsaraDB RDS for PostgreSQL instance, upgrade the major engine version of an ApsaraDB RDS for PostgreSQL instance, or create a read-only ApsaraDB RDS for PostgreSQL instance. For more information, see Restore the data of an ApsaraDB RDS for PostgreSQL instance, Upgrade the major engine version of an ApsaraDB RDS for PostgreSQL instance, or Create a read-only ApsaraDB RDS for PostgreSQL instance.
Suggestions
- The specifications of 1 core and 2 GB of memory can no longer meet the requirements for performance and stability. Therefore, the
following ApsaraDB RDS for PostgreSQL instance types that provide 1 core and 2 GB of memory will be discontinued:
pg.n2.small.2c
andrds.pg.s1.small
. You can purchase ApsaraDB RDS for PostgreSQL instances with higher specifications. - After the
pg.n2.medium.2c
instance type is discontinued, we recommend that you purchase ApsaraDB RDS for PostgreSQL instances that use thepg.x2.medium.2c
orpg.n2.2c.2m
instance type.
Note
- For more instance types, see Primary ApsaraDB RDS for PostgreSQL instance types.
- You can change the instance type by changing the specifications. For more information, see Change the specifications of an ApsaraDB RDS for PostgreSQL instance.
pg.n2.2c.2m
is a new general-purpose instance type that provides better elasticity and higher performance. This instance type accelerates instance creation and specification changes. However, this instance type does not support specific features. For more information, see the following topics:- Migrate the data of a self-managed PostgreSQL instance to an ApsaraDB RDS for PostgreSQL instance
- Configure disk encryption for an ApsaraDB RDS for PostgreSQL instance
- Configure SSL encryption for an ApsaraDB RDS for PostgreSQL instance
- Connect an ApsaraDB RDS for PostgreSQL instance to a self-managed AD domain
- Upgrade an ApsaraDB RDS for PostgreSQL instance from Basic Edition to High-availability Edition
- Enable cross-region backups for an ApsaraDB RDS for PostgreSQL instance