Quotas and limits in Managed Service for PostgreSQL
Managed Service for PostgreSQL has the following limits:
- Quotas
are organizational restrictions that can be changed by technical support. - Limits are technical limitations due to Yandex Cloud architectural features. You cannot change the limits.
If you need more resources, you can increase quotas in one of the following ways:
- Generate a request for a quota increase
. You must have thequota-manager.requestOperator
role or higher, such aseditor
oradmin
. - Contact technical support
and tell us which quotas you want increased and by how much.
Quotas
Type of limit | Value |
---|---|
Connection time-to-live | 12 hours |
Number of clusters per cloud | 16 |
Total number of processor cores for all database hosts per cloud | 96 |
Total virtual memory for all database hosts per cloud | 640 GB |
Total storage capacity for all clusters per cloud | 4096 GB |
Limits
Type of limit | Minimum value | Maximum value |
---|---|---|
Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
Number of hosts per cluster when using HDD or SSD network storage | 1 | 16 |
Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 16 |
Amount of data per host when using network SSD storage | 10 GB | 4096 GB |
Amount of data per host when using network HDD storage | 10 GB | 2048 GB |
Amount of data per host when using non-replicated SSD storage | 93 GB | 10230 GB |
Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1500 GB |
Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
Number of connections per user | 1 | 15,985 |
Number of databases per cluster | 1 | 1000 |