This topic lists the available and phased-out specifications for primary ApsaraDB RDS for PostgreSQL instances. Use these tables to select an instance type based on your workload.
For instances that use cloud disks, the available memory is less than the stated capacity because the operating system uses 500 MB to 700 MB and RDS management services use approximately 500 MB.
ApsaraDB RDS for PostgreSQL instances that use cloud disks support only VPCs. When you create an instance, set Network Type to VPC. If you use an API operation, set InstanceNetworkType to VPC. For more information, see Create an ApsaraDB RDS instance.
Specifications
For a comparison between Standard Edition and Yitian Edition, see Product types.
Actual maximum IOPS depends on the storage type, storage capacity, and instance type. For more information, see Formula for calculating maximum IOPS.
Actual maximum throughput depends on the storage type, storage capacity, and instance type. For more information, see Formula for calculating maximum throughput.
Basic Edition specifications
Standard Edition specifications
Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage space |
General-purpose | pg.n2.1c.1m | 1 CPU core, 2 GB | Scales with storage type and capacity | General-purpose types share underlying resources, so IOPS and I/O bandwidth are not guaranteed. For predictable storage performance, choose a Dedicated instance type. |
| |
pg.n1e.2c.1m | 2 CPU cores, 2 GB | 200 | ||||
pg.n2e.1c.1m | 1 CPU core, 2 GB | 50 | ||||
pg.n2e.2c.1m | 2 CPU cores, 4 GB | 400 | ||||
pg.n2.2c.1m | 2 CPU cores, 4 GB | 400 | ||||
pg.n4.2c.1m | 2 CPU cores, 8 GB | 800 | ||||
pg.n2.4c.1m | 4 CPU cores, 8 GB | 800 | ||||
pg.n4.4c.1m | 4 CPU cores, 16 GB | 1600 | ||||
pg.n4.6c.1m | 6 CPU cores, 24 GB | 2400 | ||||
Dedicated | pg.x8.medium.1 | 2 CPU cores, 16 GB | 1600 | 10000 | 128 | |
pg.x8.large.1 | 4 CPU cores, 32 GB | 3200 | 20000 | 192 | ||
pg.x8.xlarge.1 | 8 CPU cores, 64 GB | 6400 | 25000 | 256 | ||
pg.x4.2xlarge.1 | 16 CPU cores, 64 GB | 6400 | 40000 | 384 | ||
pg.x8.2xlarge.1 | 16 CPU cores, 128 GB | 12800 | 40000 | 384 | ||
pg.x4.4xlarge.1 | 32 CPU cores, 128 GB | 12800 | 60000 | 640 | ||
pg.x8.4xlarge.1 | 32 CPU cores, 256 GB | 25600 | 60000 | 640 | ||
Yitian Edition specifications
Yitian Edition requires the following:
Billing method: subscription only.
PostgreSQL version: 13 or later.
Supported storage types: enterprise SSD and premium performance disk.
Supported regions (specific zones only): China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
Availability varies by zone. Check the buy page for the latest information.
Yitian Edition instance types in the Basic Edition are designed for testing and environment validation. You cannot switch other instance types to these types.
Basic Edition Yitian instance types have low specifications. For production environments, upgrade to a higher Basic Edition specification, or switch to the High-availability Edition.
Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage space |
General-purpose | pg.n1e.2c.1m | 2 CPU cores, 2 GB | 200 | General-purpose types share underlying resources, so IOPS and I/O bandwidth are not guaranteed. For predictable storage performance, choose a Dedicated instance type in the Basic Edition (Standard Edition) or a Dedicated instance type in the High-availability Edition (Yitian Edition). |
| |
pg.n2e.2c.1m | 2 CPU cores, 4 GB | 400 | ||||
High-availability Edition specifications
Standard Edition specifications
Yitian Edition specifications
Yitian Edition requires the following:
PostgreSQL version: 13 or later.
Storage type: PL1 ESSD, PL2 ESSD, or PL3 ESSD.
Supported regions (specific zones only): China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
NoteAvailability varies by zone. Check the buy page for the latest information.
Notes
Yitian Edition does not support Babelfish for RDS PostgreSQL.
You can switch from a Standard Edition instance type to a Yitian Edition instance type. For more information, see Change specifications.
Specifications
Series | Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage space |
High-availability series | General-purpose | pg.n4m.2c.2m | 2 CPU cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, select a Dedicated instance type. |
| |
pg.n4m.4c.2m | 4 CPU cores, 16 GB | 1600 | |||||
pg.n4m.8c.2m | 8 CPU cores, 32 GB | 3200 | |||||
pg.n2m.2c.2m | 2 CPU cores, 4 GB | 400 | |||||
pg.n2m.4c.2m | 4 CPU cores, 8 GB | 800 | |||||
pg.n2m.8c.2m | 8 CPU cores, 16 GB | 1600 | |||||
Dedicated | pg.x2m.medium.2c | 2 CPU cores, 4 GB | 400 | 20000 | 192 | ||
pg.x4m.medium.2c | 2 CPU cores, 8 GB | 800 | 20000 | 192 | |||
pg.x8m.medium.2c | 2 CPU cores, 16 GB | 1600 | 20000 | 192 | |||
pg.x2m.large.2c | 4 CPU cores, 8 GB | 800 | 40000 | 256 | |||
pg.x4m.large.2c | 4 CPU cores, 16 GB | 1600 | 40000 | 256 | |||
pg.x8m.large.2c | 4 CPU cores, 32 GB | 3200 | 40000 | 256 | |||
pg.x2m.xlarge.2c | 8 CPU cores, 16 GB | 1600 | 50000 | 384 | |||
pg.x4m.xlarge.2c | 8 CPU cores, 32 GB | 3200 | 50000 | 384 | |||
pg.x8m.xlarge.2c | 8 CPU cores, 64 GB | 6400 | 50000 | 384 | |||
pg.x2m.2xlarge.2c | 16 CPU cores, 32 GB | 3200 | 80000 | 640 | |||
pg.x4m.2xlarge.2c | 16 CPU cores, 64 GB | 6400 | 80000 | 640 | |||
pg.x8m.2xlarge.2c | 16 CPU cores, 128 GB | 12800 | 80000 | 640 | |||
pg.x2m.4xlarge.2c | 32 CPU cores, 64 GB | 6400 | 125000 | 1024 | |||
pg.x4m.4xlarge.2c | 32 CPU cores, 128 GB | 12800 | 125000 | 1024 | |||
pg.x8m.4xlarge.2c | 32 CPU cores, 256 GB | 25600 | 125000 | 1024 | |||
pg.x2m.8xlarge.2c | 64 CPU cores, 128 GB | 12800 | 240000 | 2048 | |||
pg.x4m.8xlarge.2c | 64 CPU cores, 256 GB | 25600 | 240000 | 2048 | |||
pg.x8m.8xlarge.2c | 64 CPU cores, 512 GB | 51200 | 240000 | 2048 | |||
Cluster Edition specifications
Standard Edition specifications
Yitian Edition specifications
To purchase a Yitian Edition instance type, your instance must meet the following requirements:
The major version of the instance is RDS PostgreSQL 14 or later.
The storage type of the instance is PL1 ESSD, PL2 ESSD, or PL3 ESSD.
The instance resides in one of the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
NoteYitian Edition instance types are available in only a few regions. More regions and zones will be supported. For the latest information, check the buy page.
Notes
Yitian Edition instance types do not support the Babelfish for RDS PostgreSQL feature.
You can change the instance type of an ApsaraDB RDS for PostgreSQL instance from Standard Edition to Yitian Edition. For more information, see Change specifications.
Specifications
Series | Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage space |
Cluster Edition | General-purpose | pg.n4e.2c.xc | 2 CPU cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, select a Dedicated instance type. |
| |
pg.n4e.4c.xc | 4 CPU cores, 16 GB | 1600 | |||||
pg.n4e.8c.xc | 8 CPU cores, 32 GB | 3200 | |||||
pg.n2e.2c.xc | 2 CPU cores, 4 GB | 400 | |||||
pg.n2e.4c.xc | 4 CPU cores, 8 GB | 800 | |||||
pg.n2e.8c.xc | 8 CPU cores, 16 GB | 1600 | |||||
Dedicated | pg.x2e.medium.xc | 2 CPU cores, 4 GB | 400 | 20000 | 192 | ||
pg.x4e.medium.xc | 2 CPU cores, 8 GB | 800 | 20000 | 192 | |||
pg.x8e.medium.xc | 2 CPU cores, 16 GB | 1600 | 20000 | 192 | |||
pg.x2e.large.xc | 4 CPU cores, 8 GB | 800 | 40000 | 256 | |||
pg.x4e.large.xc | 4 CPU cores, 16 GB | 1600 | 40000 | 256 | |||
pg.x8e.large.xc | 4 CPU cores, 32 GB | 3200 | 40000 | 256 | |||
pg.x2e.xlarge.xc | 8 CPU cores, 16 GB | 1600 | 50000 | 384 | |||
pg.x4e.xlarge.xc | 8 CPU cores, 32 GB | 3200 | 50000 | 384 | |||
pg.x8e.xlarge.xc | 8 CPU cores, 64 GB | 6400 | 50000 | 384 | |||
pg.x2e.2xlarge.xc | 16 CPU cores, 32 GB | 3200 | 80000 | 640 | |||
pg.x4e.2xlarge.xc | 16 CPU cores, 64 GB | 6400 | 80000 | 640 | |||
pg.x8e.2xlarge.xc | 16 CPU cores, 128 GB | 12800 | 80000 | 640 | |||
pg.x2e.4xlarge.xc | 32 CPU cores, 64 GB | 6400 | 125000 | 1024 | |||
pg.x4e.4xlarge.xc | 32 CPU cores, 128 GB | 12800 | 125000 | 1024 | |||
pg.x8e.4xlarge.xc | 32 CPU cores, 256 GB | 25600 | 125000 | 1024 | |||
pg.x2e.8xlarge.xc | 64 CPU cores, 128 GB | 12800 | 240000 | 2048 | |||
pg.x4e.8xlarge.xc | 64 CPU cores, 256 GB | 25600 | 240000 | 2048 | |||
pg.x8e.8xlarge.xc | 64 CPU cores, 512 GB | 51200 | 240000 | 2048 | |||
Phased-out instance types
The following table lists the phased-out instance types for ApsaraDB RDS for PostgreSQL. These instance types are no longer available for new instances. We recommend that you use the latest instance types.