This topic describes the current and historical instance types for primary ApsaraDB RDS for PostgreSQL instances.
For RDS instances that use cloud disks, the memory includes the memory that is occupied by the underlying operating system and the memory that is occupied by the RDS-related management services. Therefore, the available memory of an RDS instance may be less than the memory capacity that is supported by the instance type. The following list describes the memory that is occupied by the underlying operating system and the memory that is occupied by the RDS-related management services:
The underlying operating system occupies 500 MB to 700 MB of memory.
The RDS-related management services occupy approximately 500 MB of memory.
RDS PostgreSQL instances that use cloud disks support only the virtual private cloud (VPC) network type. When you create an instance, set the Network Type parameter to VPC. If you configure the instance using an API operation, set the InstanceNetworkType parameter to VPC. For more information, see Create an ApsaraDB RDS instance.
Specifications checklist
For more information about the differences between Standard Edition and Yitian Edition, see Product types.
Actual maximum IOPS: The 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: The actual maximum throughput depends on the storage type, storage capacity, and instance type. For more information, see Formula for calculating maximum throughput.
Basic Series Specifications
Standard Edition Specifications
Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage capacity |
General-purpose | pg.n2.2c.1m | 2 cores, 4 GB | 400 | The maximum IOPS and I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, select a dedicated instance type. |
| |
pg.n4.2c.1m | 2 cores, 8 GB | 800 | ||||
pg.n2.4c.1m | 4 cores, 8 GB | 800 | ||||
pg.n4.4c.1m | 4 cores, 16 GB | 1,600 | ||||
pg.n4.6c.1m | 6 cores, 24 GB | 2,400 | ||||
pg.n4.8c.1m | 8 cores, 32 GB | 3,200 | ||||
Dedicated | pg.x8.medium.1 | 2 cores, 16 GB | 1,600 | 10,000 | 128 | |
pg.x8.large.1 | 4 cores, 32 GB | 3,200 | 20,000 | 192 | ||
pg.x8.xlarge.1 | 8 cores, 64 GB | 6,400 | 25,000 | 256 | ||
pg.x4.2xlarge.1 | 16 cores, 64 GB | 6,400 | 40,000 | 384 | ||
pg.x8.2xlarge.1 | 16 cores, 128 GB | 12,800 | 40,000 | 384 | ||
pg.x4.4xlarge.1 | 32 cores, 128 GB | 12,800 | 60,000 | 640 | ||
pg.x8.4xlarge.1 | 32 cores, 256 GB | 25,600 | 60,000 | 640 | ||
Yitian Edition instance types
To purchase a Yitian Edition instance type, your instance must meet the following requirements:
Billing method: subscription.
Major engine version: PostgreSQL 13 or later.
The storage types for the instance are enterprise SSD and premium performance disk.
Region (only specific zones are available): China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
Yitian Edition instance types are available in only a few regions. More regions and zones will be supported. For the latest information, see the buy page.
Yitian Edition instance types of RDS Basic Edition are intended for testing and environment validation. You cannot change other instance types to these instance types.
The specifications of Yitian Edition instance types of RDS Basic Edition are relatively low. If you want to use these instance types in a production environment, upgrade the instance specifications to a higher instance type of RDS Basic Edition, or upgrade the instance to the High-availability Edition.
Family | Instance Type Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage capacity |
General-purpose | pg.n1e.2c.1m | 2 cores, 2 GB | 200 | The maximum IOPS and I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, select a dedicated instance type of Standard Edition on RDS Basic Edition or a dedicated instance type of Yitian Edition on RDS High-availability Edition. |
| |
pg.n2e.2c.1m | 2 cores, 4 GB | 400 | ||||
High-availability Edition instance types
Standard Edition Specifications
Yitian edition specifications
To purchase a Yitian Edition instance type, your instance must meet the following requirements:
Major engine version: PostgreSQL 13 or later.
Storage type: PL1 ESSD, PL2 ESSD, or PL3 ESSD.
Region: 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, see 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 a Standard Edition instance type to a Yitian Edition instance type. For more information, see Change the specifications of an ApsaraDB RDS for PostgreSQL instance.
Instance types
Series | Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage capacity |
High-availability Edition | General-purpose | pg.n4m.2c.2m | 2 cores, 8 GB | 800 | The maximum IOPS and I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, select a dedicated instance type. |
| |
pg.n4m.4c.2m | 4 cores, 16 GB | 1,600 | |||||
pg.n4m.8c.2m | 8 cores, 32 GB | 3,200 | |||||
pg.n2m.2c.2m | 2 cores, 4 GB | 400 | |||||
pg.n2m.4c.2m | 4 cores, 8 GB | 800 | |||||
pg.n2m.8c.2m | 8 cores, 16 GB | 1,600 | |||||
Dedicated | pg.x2m.medium.2c | 2 cores, 4 GB | 400 | 20,000 | 192 | ||
pg.x4m.medium.2c | 2 cores, 8 GB | 800 | 20,000 | 192 | |||
pg.x8m.medium.2c | 2 cores, 16 GB | 1,600 | 20,000 | 192 | |||
pg.x2m.large.2c | 4 cores, 8 GB | 800 | 40,000 | 256 | |||
pg.x4m.large.2c | 4 cores, 16 GB | 1,600 | 40,000 | 256 | |||
pg.x8m.large.2c | 4 cores, 32 GB | 3,200 | 40,000 | 256 | |||
pg.x2m.xlarge.2c | 8 cores, 16 GB | 1,600 | 50,000 | 384 | |||
pg.x4m.xlarge.2c | 8 cores, 32 GB | 3,200 | 50,000 | 384 | |||
pg.x8m.xlarge.2c | 8 cores, 64 GB | 6,400 | 50,000 | 384 | |||
pg.x2m.2xlarge.2c | 16 cores, 32 GB | 3,200 | 80,000 | 640 | |||
pg.x4m.2xlarge.2c | 16 cores, 64 GB | 6,400 | 80,000 | 640 | |||
pg.x8m.2xlarge.2c | 16 cores, 128 GB | 12,800 | 80,000 | 640 | |||
pg.x2m.4xlarge.2c | 32 cores, 64 GB | 6,400 | 125,000 | 1,024 | |||
pg.x4m.4xlarge.2c | 32 cores, 128 GB | 12,800 | 125,000 | 1,024 | |||
pg.x8m.4xlarge.2c | 32 cores, 256 GB | 25,600 | 125,000 | 1,024 | |||
pg.x2m.8xlarge.2c | 64 cores, 128 GB | 12,800 | 240,000 | 2,048 | |||
pg.x4m.8xlarge.2c | 64 cores, 256 GB | 25,600 | 240,000 | 2,048 | |||
pg.x8m.8xlarge.2c | 64 cores, 512 GB | 51,200 | 240,000 | 2,048 | |||
Cluster Edition instance types
Standard Edition Specifications
Yitian Edition Specifications
To purchase a Yitian Edition instance type, your instance must meet the following requirements:
Major engine version: PostgreSQL 14 or later.
Storage type: PL1 ESSD, PL2 ESSD, or PL3 ESSD.
Region: 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, see 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 a Standard Edition instance type to a Yitian Edition instance type. For more information, see Change the specifications of an ApsaraDB RDS for PostgreSQL instance.
Instance types
Edition | Family | Specification Code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage capacity |
Cluster Edition | General-purpose | pg.n4e.2c.xc | 2 cores, 8 GB | 800 | The maximum IOPS and I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, select a dedicated instance type. |
| |
pg.n4e.4c.xc | 4 cores, 16 GB | 1,600 | |||||
pg.n4e.8c.xc | 8 cores, 32 GB | 3,200 | |||||
pg.n2e.2c.xc | 2 cores, 4 GB | 400 | |||||
pg.n2e.4c.xc | 4 cores, 8 GB | 800 | |||||
pg.n2e.8c.xc | 8 cores, 16 GB | 1,600 | |||||
Dedicated | pg.x2e.medium.xc | 2 cores, 4 GB | 400 | 20,000 | 192 | ||
pg.x4e.medium.xc | 2 cores, 8 GB | 800 | 20,000 | 192 | |||
pg.x8e.medium.xc | 2 cores, 16 GB | 1,600 | 20,000 | 192 | |||
pg.x2e.large.xc | 4 cores, 8 GB | 800 | 40,000 | 256 | |||
pg.x4e.large.xc | 4 cores, 16 GB | 1,600 | 40,000 | 256 | |||
pg.x8e.large.xc | 4 cores, 32 GB | 3,200 | 40,000 | 256 | |||
pg.x2e.xlarge.xc | 8 cores, 16 GB | 1,600 | 50,000 | 384 | |||
pg.x4e.xlarge.xc | 8 cores, 32 GB | 3,200 | 50,000 | 384 | |||
pg.x8e.xlarge.xc | 8 cores, 64 GB | 6,400 | 50,000 | 384 | |||
pg.x2e.2xlarge.xc | 16 cores, 32 GB | 3,200 | 80,000 | 640 | |||
pg.x4e.2xlarge.xc | 16 cores, 64 GB | 6,400 | 80,000 | 640 | |||
pg.x8e.2xlarge.xc | 16 cores, 128 GB | 12,800 | 80,000 | 640 | |||
pg.x2e.4xlarge.xc | 32 cores, 64 GB | 6,400 | 125,000 | 1,024 | |||
pg.x4e.4xlarge.xc | 32 cores, 128 GB | 12,800 | 125,000 | 1024 | |||
pg.x8e.4xlarge.xc | 32 cores, 256 GB | 25,600 | 125,000 | 1,024 | |||
pg.x2e.8xlarge.xc | 64 cores, 128 GB | 12,800 | 240,000 | 2,048 | |||
pg.x4e.8xlarge.xc | 64 cores, 256 GB | 25,600 | 240,000 | 2,048 | |||
pg.x8e.8xlarge.xc | 64 cores, 512 GB | 51,200 | 240,000 | 2,048 | |||
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. Use the latest instance types.