Starting January 31, 2023, some general-purpose instance types are no longer available for purchase when you create ApsaraDB RDS for PostgreSQL instances that run RDS Basic Edition due to product optimization and adjustment.
Background information
We recommend that you select the new general-purpose instance types for your RDS instances. The new general-purpose instance types deliver better scalability and performance and reduce the time to create an RDS instance or change the specifications of an RDS instance. For more information, see Primary ApsaraDB RDS for PostgreSQL instance types (x86).
Both the general-purpose instance types and the new general-purpose instance types of the RDS instances that run RDS Basic Edition are available for purchase now. From January 31, 2023, Alibaba Cloud gradually phases out the general-purpose instance types. The new general-purpose instance types will be renamed as general-purpose instance types.
Instance types that are to be phased out and effective dates
| RDS edition | Database engine version | Instance family | Instance type | Number of cores and memory capacity | Effective date |
|---|---|---|---|---|---|
| RDS Basic Edition | PostgreSQL 15, PostgreSQL 14, PostgreSQL 13, PostgreSQL 12, PostgreSQL 11, and PostgreSQL 10 | General-purpose instance family | pg.n2.small.1 | 1 core, 2 GB | January 31, 2023 |
| pg.n2.medium.1 | 2 cores, 4 GB | To be determined | |||
| pg.n4.medium.1 | 2 cores, 8 GB | ||||
| pg.n2.large.1 | 4 cores, 8 GB | ||||
| pg.n4.large.1 | 4 cores, 16 GB | ||||
| pg.n2.xlarge.1 | 8 cores, 16 GB | ||||
| pg.n4.xlarge.1 | 8 cores, 32 GB | ||||
| pg.n2.2xlarge.1 | 16 cores, 32 GB | ||||
| pg.n4.2xlarge.1 | 16 cores, 64 GB | ||||
| pg.n8.2xlarge.1 | 16 cores, 128 GB | ||||
| pg.n4.4xlarge.1 | 32 cores, 128 GB | ||||
| pg.n8.4xlarge.1 | 32 cores, 256 GB | ||||
| pg.n4.8xlarge.1 | 64 cores, 256 GB | January 31, 2023 | |||
| pg.n8.8xlarge.1 | 64 cores, 512 GB | January 31, 2023 |
Impacts and suggestions
| Category | Impact | Suggestion |
|---|---|---|
| Existing RDS instance | When you change the specifications of your existing RDS instance, restore the data of your existing RDS instance to a new RDS instance, or upgrade the major engine version of your existing RDS instance, you cannot select a phased-out instance type. For more information, see Change the specifications of an ApsaraDB RDS for PostgreSQL instance, Restore data of an ApsaraDB RDS for PostgreSQL instance, or Upgrade the major engine version of an ApsaraDB RDS for PostgreSQL instance. Other operations on your existing RDS instance are not affected. | We recommend that you select an available instance type. For example, if your existing RDS instance uses Note You cannot directly change the instance type of an RDS instance from a general-purpose instance type to a new general-purpose instance type. Alibaba Cloud will announce updates if any. |
| New RDS instance | You cannot select a phased-out instance type when you create an RDS instance. | We recommend that you select an available instance type. For more information, see Primary ApsaraDB RDS for PostgreSQL instance types (x86). Note If you call an API operation or use Terraform to create an RDS instance, we recommend that you change the value of the parameter that specifies the instance type to an available instance type. This way, the RDS instance can be successfully created even if the general-purpose instance type is phased out. |