This page lists known issues with Cloud SQL for PostgreSQL, along with ways you can avoid or recover from these issues.If you are experiencing issues with your instance, make sure you also review the information in Diagnosing Issues.
Instance connection issues
Expired SSL/TLS certificates
If your instance is configured to use SSL, go to the Cloud SQL Instances page in the Cloud Console and open the instance. Open its Connections page and make sure that your server certificate is valid. If it has expired, you must add a new certificate and rotate to it. Learn more.
Cloud SQL Proxy version
If you are connecting using the Cloud SQL Proxy, make sure you are using the most recent version. For more information, see Keeping the Cloud SQL Proxy up to date.
Not authorized to connect
If you try to connect to an instance that does not exist in that project, the error message only says that you are not authorized to access that instance.
The following only works with the default user ('postgres'):
gcloud sql connect --user
If you try to connect using this command with any other user, the error message says FATAL: database 'user' does not exist. The workaround is to connect using the default user ('postgres'), then use the
"\c"psql command to reconnect as the different user.
Long-running Cloud SQL instance operations cannot be cancelled or stopped
When you start a long-running Cloud SQL instance operation, such as an import or export operation, you cannot stop the operation before it completes. In addition, only one operation can run against an instance at at time.
For this reason, make sure you do not need to do other work on an instance when you start a long-running operation.
Instance names cannot be reused immediately after instance deletion
After you delete an instance, you cannot immediately reuse the instance name, because Cloud SQL reserves that name for a few days. If you need to create and delete instances with the same name, consider using a timestamp as part of the name to avoid name conflicts.
Issues with importing and exporting data
Exporting many large objects cause instance to become unresponsive
If your database contains many large objects (blobs), exporting the database can consume so much memory that the instance becomes unresponsive. This can happen even if the blobs are empty.