Release notes

This page lists major changes to Cloud SQL and the calendar month when they were rolled out. Because Cloud SQL is a managed service, and updates can happen over a period of time, some instances might receive an update before others.

For a list of known issues you might encounter when using Cloud SQL, see Cloud SQL Known Issues.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly: https://cloud.google.com/feeds/cloud-sql-release-notes.xml

December 13, 2019

You can now use Cloud VPN with Cloud SQL. To get started, see Using a VPN with Cloud SQL.

Connection organization policies for Cloud SQL give you the ability to set policies that control access to and from Cloud SQL instances. To learn more about this feature, see Connection organization policies. To use this feature, see Setting organization policies for Cloud SQL.

December 10, 2019

Cloud SQL now offers notifications for upcoming maintenance. See the Overview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, see Finding and setting maintenance windows.

November 25, 2019

Cloud SQL now supports Access Transparency. As part of Google's long-term commitment to security and transparency, you can use Access Transparency, which provides you with logs of actions that Google staff have taken when accessing your data. To learn more about Access Transparency, see the Overview of Access Transparency.

November 19, 2019

Cloud SQL now supports customer-managed encryption keys (CMEK). With CMEK, you can encrypt Cloud SQL instances using a key you manage. To learn more about CMEK, see the Overview of customer managed encryption keys (CMEK). To start using CMEK, see Using customer-managed encryption keys (CMEK).

October 18, 2019

Cloud SQL Second Generation MySQL instances have a new high availability (HA) configuration. The new HA configuration, based on Google's Regional Disks, eliminates replication lag and, combined with automatic failover, provides isolation from many types of infrastructure, hardware, and software failures. Regional disks also ensure that all previously committed database transactions are persisted and available after failover, right up to the time of the failure.

The new high availability configuration is the default. You can continue to use the API to create instances with the legacy high availability configuration (using failover replicas) until the upgrade of existing instances occurs in early 2020. To learn how high availability now works for Second Generation MySQL instances, see the Overview of the high availability configuration. To enable high availability on existing instances, or to create new instances with high availability, see Enabling and disabling high availability on an instance.

October 15, 2019

The beta version of Cloud SQL for SQL Server is available. To begin creating SQL Server instances, see Creating Instances.

September 27, 2019

PostgreSQL version 11 is now generally available. PostgreSQL 11 is the default version when creating new instances. To start using PostgreSQL 11, see Creating Instances.

June 25, 2019

This release increases the maximum data storage for instances of MySQL (MySQL Second Generation) and PostgreSQL. The maximum data storage is increased from 10,230 GB to 30,720 GB. For Cloud SQL storage limits, see Limits. You can limit your automatic storage increases; see Automatic storage increase limit.

May 24, 2019

Cloud SQL now allows you to specify a location for backups, and to restrict data to a single region. To learn about custom backup locations, see Custom backup locations. To learn how to set a custom location for a backup, see Setting and viewing a custom location for backups.

April 18, 2019

Support for asia-northeast2 region (Osaka, Japan).

April 9, 2019

Cloud SQL now supports PostgreSQL version 11.1 Beta. To start using PostgreSQL 11 Beta, see Creating Instances.

April 3, 2019

Support added for 122 MySQL flags and 96 PostgreSQL flags. See Supported PostgreSQL Flags and Supported MySQL Flags.

March 11, 2019

Support for europe-west6 region (Zürich, Switzerland).

February 13, 2019

Cloud SQL for PostgreSQL connection limits are now double when memory is 6 GiB or higher. See the connection limits table for details.

January 29, 2019

Cloud SQL Second Generation is replacing First Generation. Support for First Generation instances for MySQL is ending March 25th, 2020.

December 6, 2018

GA support for Private IP connectivity.

November 6, 2018

Support for CSV format for PostgreSQL instance imports and exports.

October, 2018

Support for asia-east2 region (Hong Kong).

Upgrade to Second Generation generally available for eligible First Generation MySQL instances.

September, 2018

Beta support for private IP (private services access) connectivity.

Proxy version 1.12 released.

August, 2018

PostGIS extension includes full support for JSON-C.

July, 2018

Support for us-west2 region (Los Angeles).

June, 2018

Support for connecting from Cloud Functions Beta.

Support for europe-north1 region (Finland).

May, 2018

Support for asia-southeast1 region (Singapore).

April, 2018

GA support for Cloud SQL for PostgreSQL.

March, 2018

Support for europe-west4 region (Netherlands).

February, 2018

January, 2018

MySQL 5.6 minor version upgraded to 5.6.36.

Support for northamerica-northeast1 region (Montréal).

Connection limits for PostgreSQL instances changed. Learn more.

November, 2017

Beta support for the high availability configuration and replication for PostgreSQL instances.

October, 2017

Support for asia-south1 region (Mumbai).

Proxy version 1.11 released.

September, 2017

Support for 64-core machine types for MySQL instances and 64 cores for PostgreSQL instances.

Support for southamerica-east1 region (São Paulo).

August, 2017

Support for europe-west3 region (Frankfurt).

June, 2017

Support for labels.

Proxy version 1.10 released.

Support for australia-southeast1 region (Sydney).

Support for europe-west2 region (London).

Support for the following PostgreSQL extensions: btree-gin, btree-gist, chkpass, citext, cube, dict_int, dict_xsyn, earthdistance, intagg, intarray, isn, ltree, pgstattuple, pg_trgm, tablefunc, tsm_system_rows, tsm_system_time, unaccent, uuid-ossp.

May, 2017

GA support for Second Generation and PostgreSQL instances in version 157.0.0 of the gcloud command-line tool. The beta version is no longer required for these instances.

Support for us-west1 region (Oregon).

Support for us-east4 region (Northern Virginia).

April, 2017

Proxy version 1.09 released.

March, 2017

Cloud SQL for PostgreSQL Beta availability.

To provide feedback on the beta release, go to our Cloud SQL user forum.

Support for 32-core machine types for MySQL instances.

Support for making MySQL general and slow query log files available through the Stackdriver Log Viewer.

February, 2017

December, 2016

Support for administration of users and databases for Second Generation instances in the Google Cloud Console and the Cloud SQL API.

November, 2016

Support for Northeastern Asia Pacific region (asia-northeast1).

MySQL 5.7 minor version upgraded to 5.7.14.

August, 2016

Cloud SQL Second Generation General Availability.

Was this page helpful? Let us know how we did:

Send feedback about...

Cloud SQL for MySQL
Need help? Visit our support page.