This topic describes the specifications and pricing of PolarDB for PostgreSQL, including billing methods, billable items, and the pricing of compute nodes, storage, data backups, and SQL Explorer.
Billing methods
PolarDB for PostgreSQL supports the following billing methods:
- Subscription
If you use the subscription billing method, you must pay for a compute cluster when you create the cluster. The compute cluster consists of one primary node and one read-only node. You are charged for only the consumed storage. The charges are deducted from your account balance based on the consumed storage.
- Pay-as-you-go
If you use the pay-as-you-go billing method, you pay for the resources after you use them. You are charged for the compute clusters and the consumed storage by hour. The charges are deducted from your account balance based on the consumed resources.
若您在合同期内退订包年包月的集群,需要交纳相应的手续费,详细规则请参见退款规则。
Billable items
The following table describes the billable items of PolarDB for PostgreSQL clusters.
| Billable item | Description |
| Compute cluster that has a primary node and one or more read-only nodes | Subscription or pay-as-you-go. |
| Storage |
|
| SQL Explorer | After you enable SQL Explorer, the billing method is specified as pay-as-you-go. For more information, see ️SQL Explorer. |
| Data backup | In PolarDB, the backup feature is available for free. You are charged for only the storage of backup files. For more information, see Backup method 2: Manual backup. |
Compute node pricing
All the nodes of PolarDB for PostgreSQL are dedicated nodes. The dedicated nodes indicate that the CPU, memory, storage, and I/O resources that are allocated to the nodes are dedicated to these nodes and are not shared by other nodes. Therefore, the performance of the dedicated nodes is more stable and reliable. The following table describes the node specifications that are available in PolarDB for PostgreSQL.
| Node type | CPU and memory | Maximum storage capacity | Maximum number of connections | Internal network bandwidth | Maximum IOPS | I/O bandwidth |
| polar.pg.x4.medium | 2 cores 8 GB | 5 TB | 800 | 1 Gbps | 16,000 | 1 Gbps |
| polar.pg.x4.large | 4 cores 16 GB | 10 TB | 1600 | 10 Gbps | 64,000 | 4 Gbps |
| polar.pg.x4.xlarge | 8 cores 32 GB | 10 TB | 3,200 | 10 Gbps | 128,000 | 8 Gbps |
| polar.pg.x8.xlarge | 8 cores 64 GB | 30 TB | 10,000 | 10 Gbps | 160,000 | 10 Gbps |
| polar.pg.x8.2xlarge | 16 cores 128 GB | 50 TB | 12,000 | 10 Gbps | 256,000 | 16 Gbps |
| polar.pg.x8.4xlarge | 32 cores 256 GB | 50 TB | 20,000 | 10 Gbps | 384,000 | 24 Gbps |
| polar.pg.x8.8xlarge | 64 cores 512 GB | 100 TB | 51,200 | 10 Gbps | 409,600 | 24 Gbps |
| polar.pg.x8.12xlarge | 88 cores 710 GB | 100 TB | 76,800 | 25 Gbps | 512,000 | 32 Gbps |
- A cluster that has 2 CPU cores and 8 GB memory provides the basic specifications that are required in tests, trials, and other light load scenarios. We recommend that you do not use the clusters of this type in heavy-load production environments. In production environments, we recommend that you use a cluster that has 8 CPU cores and 32 GB memory or higher specifications.
- You can select a node type for the primary node when you create a cluster. The same type is automatically applied to read-only nodes.
- The maximum number of IOPS is a theoretically calculated value.
- The maximum number of connections for a cluster varies based on the node specifications of the cluster. If you add nodes to a cluster, the number of connections for the cluster does not change.
- If you have higher storage requirements, you can Submit a ticket to contact customer services to increase the maximum storage capacity to 100 TB.
配置 | 中国内地 | 中国香港 | 美国硅谷 | 新加坡 | 印度尼西亚雅加达 | 马来西亚吉隆坡 | 德国法兰克福 | 日本东京 | |
节点规格 | CPU和内存数 | ||||||||
polar.pg.x4.medium | 2核 8 GB | 280元/月 0.59元/小时 | 490元/月 1.03元/小时 | 395元/月 0.83元/小时 | 490元/月 1.03元/小时 | 475元/月 0.99元/小时 | 490元/月 1.03元/小时 | 430元/月 0.90元/小时 | 410元/月 0.86元/小时 |
polar.pg.x4.large | 4核 16 GB | 1,000元/月 2.09元/小时 | 1,900元/月 3.96元/小时 | 1,550元/月 3.23元/小时 | 1,900元/月 3.96元/小时 | 1,750元/月 3.65元/小时 | 1,900元/月 3.96元/小时 | 1,700元/月 3.55元/小时 | 1,600元/月 3.34元/小时 |
polar.pg.x4.xlarge | 8核 32 GB | 2,000元/月 4.17元/小时 | 3,800元/月 7.92元/小时 | 3,100元/月 6.46元/小时 | 3,800元/月 7.92元/小时 | 3,500元/月 7.30元/小时 | 3,800元/月 7.92元/小时 | 3,400元/月 7.09元/小时 | 3,200元/月 6.67元/小时 |
polar.pg.x8.xlarge | 8核 64 GB | 3,200元/月 6.67元/小时 | 4,800元/月 10.00元/小时 | 4,000元/月 8.34元/小时 | 4,800元/月 10.00元/小时 | 4,450元/月 9.28元/小时 | 4,800元/月 10.00元/小时 | 4,200元/月 8.75元/小时 | 4,100元/月 8.55元/小时 |
polar.pg.x8.2xlarge | 16核 128 GB | 6,400元/月 13.34元/小时 | 9,600元/月 20.00元/小时 | 8,000元/月 16.67元/小时 | 9,600元/月 20.00元/小时 | 8,900元/月 18.55元/小时 | 9,600元/月 20.00元/小时 | 8,400元/月 17.50元/小时 | 8,200元/月 17.09元/小时 |
polar.pg.x8.4xlarge | 32核 256 GB | 12,800元/月 26.67元/小时 | 19,200元/月 40.00元/小时 | 16,000元/月 33.34元/小时 | 19,200元/月 40.00元/小时 | 17,800元/月 37.09元/小时 | 19,200元/月 40.00元/小时 | 16,800元/月 35.00元/小时 | 16,400元/月 34.17元/小时 |
polar.pg.x8.8xlarge | 64核 512 GB | 28,160元/月 58.67元/小时 | 42,240元/月 88.00元/小时 | 35,200元/月 73.34元/小时 | 42,240元/月 88.00元/小时 | 39,160元/月 81.59元/小时 | 42,240元/月 88.00元/小时 | 36,960元/月 77.00元/小时 | 36,080元/月 75.17元/小时 |
polar.pg.x8.12xlarge | 88核 710 GB | 35,200元/月 73.34元/小时 | 52,800元/月 110.00元/小时 | 44,000元/月 91.67元/小时 | 52,800元/月 110.00元/小时 | 48,950元/月 101.98元/小时 | 52,800元/月 110.00元/小时 | 46,700元/月 97.30元/小时 | 45,100元/月 93.96元/小时 |
Storage pricing
Pay-as-you-go
- 中国内地地域:0.00486元/GB/小时。
- 中国香港及海外地域:0.00542元/GB/小时。
Subscription
If the data size is large, we recommend that you purchase storage plans. Compared with the pay-as-you-go billing method, subscription-based storage plans offer additional discounts. Higher discounts are provided for larger storage plans. For more information about how to purchase a storage plan, see Purchase a storage plan.
Data backup pricing
The backup and restoration features of PolarDB for PostgreSQL are available for free. Only storage fees are charged. In PolarDB for PostgreSQL, the storage fees are calculated based on the storage that is consumed by the backup files of data and logs and the retention periods of these backup files.
| Backup type | Free quota | Billing rule |
| Level-1 backups | Database storage usage × 50% You can view the database storage usage of a cluster on the Overview page of the cluster in the PolarDB console. | Storage fee per hour = (Total physical storage of level-1 backups - Free quota) × Unit price per hour
For example, if the total physical storage of level-1 backups is 700 GB and the database storage usage is 1,000 GB, the storage fee per hour is USD 0.0928. 计算公式:[700 GB-(1000 GBx50%)]x0.003元=0.6元 |
| Level-2 backups | None. | Storage fee per hour = Total physical storage of level-2 backups × Unit price per hour For example, if the total physical storage of level-2 backups is 1,000 GB, the storage fee per hour is USD 0.0325. 计算公式:1000 GBx0.00021元=0.21元 |
| Log backups | 100 GB | Storage fee per hour = (Total physical storage of log backups - 100 GB) × Unit price per hour For example, if the total physical storage of log backups is 1,000 GB, the storage fee per hour is USD 0.02925. 计算公式:(1000 GB-100 GB)x0.00021元=0.189元 |
SQL Explorer pricing
You are charged for SQL Explorer based on the storage that is consumed by audit logs.
- 中国内地地域:0.008元/GB/小时。
- 中国香港及海外地域:0.0122元/GB/小时。
FAQ
- What is the price if I add a read-only node?
The price of a read-only node is the same as that of the primary node. For more information, see Compute node pricing.
- Is the maximum storage capacity doubled after I add a read-only node?
No, the storage capacity is not doubled after you add a read-only node. PolarDB for PostgreSQL uses an architecture where computing is decoupled from storage. The read-only nodes that you purchase are used for computing. If you add read-only nodes to your cluster, the storage capacity of the cluster does not change.
A serverless architecture is used for storage. Therefore, you do not need to select the capacity when you purchase a cluster. The capacity is automatically increased online when the amount of data increases. You are charged for only the consumed storage. The maximum storage capacity varies based on cluster specifications. If you want to increase the maximum storage capacity, upgrade your cluster specifications. For more information, see Change the specifications of a cluster.
