Quotas and limits in Managed Service for Sharded PostgreSQL
Note
The service is at the Preview stage.
Managed Service for Sharded PostgreSQL has the following limitations:
- Quotas are organizational constraints that can be changed by support on request.
- Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.
If you need more resources, you can increase your quotas in one of the following ways:
- Make a request to increase your quotas.
- Contact support and specify which quotas you want increased and by how much.
To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g., editor or admin.
You can manage your quotas with Cloud Quota Manager.
Quotas
|
Type of limit |
Value |
|
Connection TTL |
12 hours |
|
Number of clusters per cloud |
16 |
|
Total number of CPU cores for all database hosts per cloud |
64 |
|
Total virtual memory for all database hosts per cloud |
512 GB |
|
Total storage capacity for all clusters per cloud |
4,096 GB |
|
Number of GPUs |
0 |
Limits
For PostgreSQL cluster limits, see this Managed Service for PostgreSQL guide.
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m4a-c80-m640 (80 vCPU AMD Zen 3, 640 GB RAM) |
| Number of shards per cluster | 1 | No limits |
Number of INFRA hosts per cluster |
1 | 7 |
Number of ROUTER hosts per cluster |
1 | No limits |
Number of COORDINATOR hosts per cluster |
1 | 5 |