This document lists the quotas and limits that apply to AlloyDB for PostgreSQL.
A quota restricts how much of a particular shared Google Cloud resource your Cloud project can use, including hardware, software, and network components.
Quotas are part of a system that does the following:
- Monitors your use or consumption of Google Cloud products and services.
- Restricts your consumption of those resources for reasons including ensuring fairness and reducing spikes in usage.
- Maintains configurations that automatically enforce prescribed restrictions.
- Provides a means to make or request changes to the quota.
When a quota is exceeded, in most cases, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Cloud project and are shared across all applications and IP addresses that use that Cloud project.
Check your quotas
To check the current quotas for AlloyDB resources in your project, go to the Quotas page in the Google Cloud console and filter for AlloyDB API.
Request a quota increase
To increase or decrease most quotas, use the Google Cloud console. For more information, see Requesting a higher quota.
There are also limits on AlloyDB resources. These limits are unrelated to the quota system. The limits shown here apply during the preview release period and are subject to increase upon general availability of AlloyDB. To request a limit increase during the preview release period, contact the Google Cloud sales team.
|Clusters per project per region||3|
|vCPUs per project per region||1,100|
|Read pool nodes per cluster (across all read pool instances)||20 (15 if all nodes are of the 64 vCPU machine type)|
|Database storage per cluster||5 TiB|
|Maximum concurrent connections per instance||
Defaults to 1,000; adjustable up to 240,000
For more information, see Maximum concurrent connections.
Maximum concurrent connections
AlloyDB limits an instance's maximum
concurrent connections to 1,000, unless you set its
max_connections flag to
a higher value. You can adjust the value of this flag
to as high as 240,000.
When setting the
max_connections flag on a read pool instance, the new value
must match or exceed the
max_connections value of its cluster's primary