This page provides information about the Cloud SQL quotas and limits. Quotas are applied per-project; limits are applied to the instance or to the project, depending on the limit.
Checking your quotas
To check the current quotas for resources in your project, go to the Quotas page in the Google Cloud Console.
Increasing your quotas
As your use of Google Cloud expands over time, your quotas can increase accordingly. If you expect a notable upcoming increase in usage, make your request a few days in advance to ensure your quotas are adequately sized.
In the Quotas page, select Cloud SQL Admin API in the Services dropdown list.
If you do not see Cloud SQL Admin API, the Cloud SQL Admin API has not been enabled.
Select the quotas you want to change.
Click Edit quotas.
Fill out your name, email, and phone number and click Next.
Fill in your quota request and click Submit request.
You will receive a response from the Cloud SQL for PostgreSQL team within 48 hours of your request.
How resource quotas are replenished
Daily quotas are replenished daily at midnight Pacific time.
Quotas and resource availability
Resource quotas are the maximum amount of resources you can create for that resource type if those resources are available. Quotas do not guarantee that resources will be available at all times. If a resource is not physically available for your region, you will not be able to create new resources of that type, even if you still have remaining quota in your project.
There are restrictions on some Cloud SQL resources that are not replenished periodically and not shown on the Quotas page in the Google Cloud Console. Some limits can be increased while others cannot.
Instances per project
By default, you can have up to 40 instances per project. If you need more, file a support case to request the increase.
Maximum concurrent connections
You can use the
max_connections flag to configure connections limits. The Cloud SQL
team recommends using the default connection limits to ensure instance stability.
When you create a Cloud SQL for PostgreSQL instance, the machine type configuration settings automatically adjust the range of memory sizes available, based on the number of cores you select. This also determines the initial default connection limits set for the instance.
You can find the connection limits for your instance by connecting to your
database and running this command:
SELECT * FROM pg_settings WHERE name = 'max_connections';
The value on replicas must be greater than or equal to the value on the primary. Changes on the primary propagate to replicas that have a value that is lower than the new value on the primary, or that have not been changed from the default value.
Cloud SQL for PostgreSQL connection limits
|Memory size, in GB||Defaults for maximum concurrent connections1|
|3.75 up to 6||100|
|6 up to 7.5||200|
|7.5 up to 15||400|
|15 up to 30||500|
|30 up to 60||600|
|60 up to 120||800|
|120 and above||1000|
1Cloud SQL for PostgreSQL reserves up to six of these connections for internal operations.
Cloud SQL storage limits
|MySQL instances||PostgreSQL and SQL Server instances|
|Up to 30,720 GB, depending on the machine type.||Up to 30,720 GB, depending on whether the instance has dedicated or shared vCPUs. See the Instance settings for PostgreSQL or SQL Server.|
Cloud SQL storage optionsTo configure a storage option for best performance, it's important to understand your workload and choose the appropriate disk type and size. For more information on the available choices for Cloud SQL, see instance settings.
App Engine limits
Each App Engine instance running in a standard environment cannot have more than 100 concurrent connections to an instance. For PHP 5.5 apps, the limit is 60 concurrent connections.
App Engine applications are also subject to additional App Engine quotas and limits as discussed on the App Engine Quotas page.
Cloud Run limits
Cloud Run (fully managed) services are limited to 100 connections to a Cloud SQL database. This limit applies per service instance. This means that each instance of the Cloud Run (fully managed) service can have 100 connections to the database, and as it scales the total number of connections per deployment can grow.
Cloud Function limits
Note: Cloud Functions limits concurrent executions to 1 per instance. You never have a situation where a single function instance is processing two requests at the same time. In most situations, only a single database connection is needed.