This topic describes the instance types available for ApsaraDB RDS for PostgreSQL primary instances. You can use this information to learn about the latest and historical instance types.
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.
ApsaraDB RDS for PostgreSQL instances that use cloud disks support only virtual private clouds (VPCs). When you create an instance, you must set the network type to VPC. If you use an API operation to create an instance, you must set the InstanceNetworkType parameter to VPC. For more information, see Create an ApsaraDB RDS instance.
Specifications
For more information about the differences between Standard Edition and Yitian Edition, see Product types.
Actual maximum IOPS: The actual maximum IOPS is affected by the storage class, storage capacity, and instance type. For more information, see Formula for calculating the maximum IOPS.
Actual maximum throughput: The actual maximum throughput is affected by the storage class, storage capacity, and instance type. For more information, see Formula for calculating the maximum throughput.
Basic Edition instance types
Standard Edition instance types
Family | Instance type code | CPU and memory | Maximum connections | Maximum IOPS | Maximum I/O bandwidth (MB/s) | Storage capacity |
General-purpose | pg.n2.2c.1m | 2 CPU cores, 4 GB | 400 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, we recommend that you select a dedicated instance type. |
| |
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 | ||||
pg.n4.8c.1m | 8 CPU cores, 32 GB | 3200 | ||||
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 instance types
To purchase an instance of a Yitian Edition instance type, you must meet the following requirements:
Billing method: subscription.
Major engine version: ApsaraDB RDS for PostgreSQL 13 or later.
Storage class: enterprise SSD (ESSD) and premium performance disk.
Region (only some zones are available): China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
Yitian Edition instance types are available in a limited number of regions. More regions and zones will be supported. For more information, see the buy page.
Basic Edition Yitian instance types are used for testing and environment authentication. You cannot change the instance types of other instances to these instance types.
Basic Edition Yitian instance types have low specifications. If you want to use them in a production environment, we recommend that you upgrade the instance configurations to a higher instance type of the 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 CPU cores, 2 GB | 200 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, we recommend that you select a dedicated instance type of Basic Edition Standard Edition or a dedicated instance type of High-availability Edition Yitian Edition. |
| |
pg.n2e.2c.1m | 2 CPU cores, 4 GB | 400 | ||||
High-availability Edition instance types
Standard Edition instance types
Yitian Edition instance types
To purchase an instance of a Yitian Edition instance type, you must meet the following requirements:
Major engine version: ApsaraDB RDS for PostgreSQL 13 or later.
Storage class: 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 a limited number of regions. More regions and zones will be supported. For more information, see the buy page.
Notes
Yitian Edition instance types do not support the Babelfish for ApsaraDB for 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 instance configurations.
Instance types
Edition | Family | Instance type 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 CPU cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, we recommend that you 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 instance types
Standard Edition instance types
Yitian Edition instance types
To purchase an instance of a Yitian Edition instance type, you must meet the following requirements:
Major engine version: ApsaraDB RDS for PostgreSQL 14 or later.
Storage class: 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 a limited number of regions. More regions and zones will be supported. For more information, see the buy page.
Notes
Yitian Edition instance types do not support the Babelfish for ApsaraDB for 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 instance configurations.
Instance types
Edition | Family | Instance type 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 CPU cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your business is sensitive to IOPS, we recommend that you 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 | |||
Historical instance types
The following table lists the historical instance types for ApsaraDB RDS for PostgreSQL. You can no longer create instances of these historical instance types. We recommend that you use the latest instance types.