You can see the latest product updates for all of Google Cloud on the Google Cloud page, or browse and filter all release notes in the Google Cloud Console.
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
April 06, 2021
Cloud SQL for PostgreSQLCloud SQL for PostgreSQL now lets you use IAM database authentication with the Cloud SQL Auth proxy. The Cloud SQL Auth proxy is able to request and refresh OAuth 2.0 access tokens, ensuring that long-lived processes or applications that rely on connection pooling can have stable connections. To learn more, see Using IAM database authentication with the Cloud SQL Auth proxy.
Cloud SQL for SQL Server enables you to perform change data capture (CDC) operations for your Cloud SQL instances. General information about CDC in SQL Server is here.
CDC is available for the following Cloud SQL for SQL Server database versions:
- SQL Server 2017 Standard
- SQL Server 2017 Enterprise
After connecting to an instance, the sqlserver
user can do many CDC operations. The functions include (and are not limited to) the following:
To turn on this feature for a database, run this command:
exec msdb.[dbo].[gcloudsql_cdc_enable_db] 'demo'
To turn off this feature for a database, run this command:
exec msdb.[dbo].[gcloudsql_cdc_disable_db] 'demo'
Cloud SQL for SQL Server enables you to perform common operations on a tempdb database.
After you connect to an instance, the sqlserver
user can manage the tempdb files. Specifically, the user has the CONTROL
permission on the tempdb database, and can do many operations, including (and not limited to) the following:
* ALTER DATABASE [tempdb] ADD FILE
* ALTER DATABASE [tempdb] REMOVE
March 31, 2021
Cloud SQL for PostgreSQLCloud SQL for PostgreSQL flags are now generally available. See supported PostgreSQL flags for more information.
March 29, 2021
Cloud SQL for SQL ServerYou can integrate Cloud SQL for SQL Server with Managed Service for Microsoft Active Directory.
Authentication, authorization, and more are available. For example, joining an instance to a managed Active Directory domain enables you to log in using Windows Authentication. Additionally, you can integrate with your on-premises AD domains by establishing a trust.
March 24, 2021
Cloud SQL for MySQLSupport for europe-central2 (Warsaw ).
Support for europe-central2 (Warsaw ).
Support for europe-central2 (Warsaw ).
March 19, 2021
Cloud SQL for PostgreSQLThe following extensions in Cloud SQL for PostgreSQL are generally available:
- pg_partman. Enables you to create and manage time-based and serial-based table partition sets.
- pgTAP. Provides a unit testing framework for PostgreSQL, written in PL/pgSQL and PL/SQL.
March 12, 2021
Cloud SQL for MySQLCloud SQL for MySQL now supports the innodb_buffer_pool_size flag. To learn more about how to set this flag, see buffer pool size.
March 05, 2021
Cloud SQL for MySQLThe following MySQL minor versions have been upgraded:
- MySQL 5.6.47 is upgraded to 5.6.50
- MySQL 5.7.25 is upgraded to 5.7.32
Cloud SQL for MySQL now supports flexible instance configurations. Compared to our predefined machine types, flexible instance configurations offer you the extra freedom to configure your instance with the specific number of vCPUs and GB of RAM that fits your workload. To set up a new instance with a flexible instance configuration, see our documentation here.
February 24, 2021
Cloud SQL for MySQLCloud SQL now offers faster maintenance, with average connectivity loss lasting 90 seconds or less on average. See more about maintenance timelines.
Cloud SQL now offers faster maintenance, with average connectivity loss lasting 90 seconds or less on average. See more about maintenance timelines.
February 22, 2021
Cloud SQL for PostgreSQLThe following PostgreSQL minor versions are now available. If you use maintenance windows, you might not yet have the minor version. In this case, you will see the new minor version once your maintenance update occurs. To find your maintenance window or manage maintenance updates, see Finding and setting maintenance windows.
- PostgreSQL 9.6.19 is upgraded to 9.6.20.
- PostgreSQL 10.14 is upgraded to 10.15.
- PostgreSQL 11.9 is upgraded to 11.10.
- PostgreSQL 12.4 is upgraded to 12.5.
- PostgreSQL 13 is upgraded to 13.1.
February 10, 2021
Cloud SQL for MySQLThe Cloud SQL Admin API v1beta4 is now generally available. The URL for the Admin API will continue to refer to v1beta4 for backward compatibility. To start using the Cloud SQL Admin API now, see Using the Cloud SQL Admin API.
The Cloud SQL Admin API v1beta4 is now generally available. The URL for the Admin API will continue to refer to v1beta4 for backward compatibility. To start using the Cloud SQL Admin API now, see Using the Cloud SQL Admin API.
The Cloud SQL Admin API v1beta4 is now generally available. The URL for the Admin API will continue to refer to v1beta4 for backward compatibility. To start using the Cloud SQL Admin API now, see Using the Cloud SQL Admin API.
January 28, 2021
Cloud SQL for PostgreSQLQuery Insights is now generally available. Query Insights helps you detect, diagnose, and prevent query performance problems for Cloud SQL databases. It provides self-service, intuitive monitoring, and diagnostic information that goes beyond detection to help you to identify the root cause of performance problems.
To learn more, see Overview of Query Insights. To get started now, see Troubleshooting query performance problems using Query Insights.
January 19, 2021
Cloud SQL for PostgreSQLDatabase auditing in Cloud SQL for PostgreSQL is generally available, through the open-source pgAudit extension. Using this extension, you can selectively record and track SQL operations performed against a given database instance.
The pgAudit extension helps you configure many of the logs often required to comply with government, financial, and ISO certifications.
January 13, 2021
Cloud SQL for MySQLCloud SQL now exposes the metric database/memory/total_usage
. This metric provides visibility into the database working set (including buffer cache). You can find this metric in the Metrics explorer within the Monitoring dashboard.
For more information about database/memory/total_usage
, see Cloud SQL Metrics.
Cloud SQL now exposes the metric database/memory/total_usage
. This metric provides visibility into the database working set (including buffer cache). You can find this metric in the Metrics explorer within the Monitoring dashboard.
For more information about database/memory/total_usage
, see Cloud SQL Metrics.
Cloud SQL now exposes the metric database/memory/total_usage
. This metric provides visibility into the database working set (including buffer cache). You can find this metric in the Metrics explorer within the Monitoring dashboard.
For more information about database/memory/total_usage
, see Cloud SQL Metrics.
December 21, 2020
Cloud SQL for PostgreSQLIAM database authentication for Cloud SQL for PostgreSQL is now generally available. To get started using IAM database authentication, see the Overview of Cloud SQL IAM database authentication.
December 17, 2020
Cloud SQL for MySQLIn Cloud SQL for MySQL, parallel replication is generally available for improving replication performance.
Cloud SQL has expanded support for PostgreSQL extensions. Three additional PostgreSQL extensions are now available:
- dblink
- ip4r
- prefix
For additional information, see PostgreSQL extensions.
The following PostgreSQL minor versions have been upgraded:
- PostgreSQL 9.6.18 is upgraded to 9.6.19.
- PostgreSQL 10.13 is upgraded to 10.14.
- PostgreSQL 11.8 is upgraded to 11.9.
- PostgreSQL 12.3 is upgraded to 12.4.
December 16, 2020
Cloud SQL for PostgreSQLCloud SQL for PostgreSQL now supports the effective_cache_size flag.
November 19, 2020
Cloud SQL for MySQLCloud SQL for MySQL now supports retention settings for automated backups. You can configure retention of your automated backups for shorter or longer periods (1 to 365 days). The default setting remains 7 days.
Cloud SQL for MySQL now supports retention settings for point-in-time recovery. You have the option of retaining logs, used for point-in-time recovery, for shorter periods (1 to 7 days). The default setting is 7 days.
Cloud SQL for PostgreSQL now supports retention settings for automated backups. You can configure retention of your automated backups for shorter or longer periods (1 to 365 days). The default setting remains 7 days.
Cloud SQL for PostgreSQL now supports retention settings for point-in-time recovery. You have the option of retaining logs, used for point-in-time recovery, for shorter periods (1 to 7 days). The default setting is 7.
Cloud SQL for SQL Server now supports retention settings for automated backups. You can configure retention of your automated backups for shorter or longer periods (1 to 365 days). The default setting remains 7 days.
November 05, 2020
Cloud SQL for PostgreSQLPostgreSQL version 13 is now generally available. To start using PostgreSQL 13, see Creating instances.
October 30, 2020
Cloud SQL for MySQLIn Cloud SQL for MySQL, 80 supported flags that previously were in beta are now generally available.
October 21, 2020
Cloud SQL for MySQLCloud SQL for MySQL supports binary logging on read replicas for MySQL versions 5.7 and 8.0.
October 12, 2020
Cloud SQL for MySQLCloud SQL now offers "deny maintenance periods". With deny maintenance periods, you can prevent automatic maintenance from occurring during a specific time period. For example, the end-of-year holiday season is a time of peak load that requires heightened focus on infrastructure stability for many retail businesses. By setting a deny maintenance period from mid-October to mid-January, these businesses can prevent planned upgrades from Cloud SQL during their busiest time of year.
Cloud SQL for PostgreSQL now offers IAM database authentication to help you better monitor and manage access for users and service accounts to databases. This feature allows users and service accounts to use IAM credentials to log into PostgreSQL instances. To learn more about how IAM database authentication works, see the Overview of Cloud SQL IAM database authentication. To configure an instance, see Configuring instances for IAM database authentication. To create users or service accounts, see Creating and managing users that use IAM database authentication.
Cloud SQL now offers "deny maintenance periods". With deny maintenance periods, you can prevent automatic maintenance from occurring during a specific time period. For example, the end-of-year holiday season is a time of peak load that requires heightened focus on infrastructure stability for many retail businesses. By setting a deny maintenance period from mid-October to mid-January, these businesses can prevent planned upgrades from Cloud SQL during their busiest time of year.
Database auditing in Cloud SQL for PostgreSQL is available through the open-source pgAudit extension. Using this extension, you can selectively record and track SQL operations performed against a given database instance.
The pgAudit extension helps you configure many of the logs often required to comply with government, financial, and ISO certifications.
Cloud SQL now offers "deny maintenance periods". With deny maintenance periods, you can prevent automatic maintenance from occurring during a specific time period. For example, the end-of-year holiday season is a time of peak load that requires heightened focus on infrastructure stability for many retail businesses. By setting a deny maintenance period from mid-October to mid-January, these businesses can prevent planned upgrades from Cloud SQL during their busiest time of year.
September 24, 2020
Cloud SQL for MySQLMySQL 5.6.42 is upgraded to 5.6.47.
September 21, 2020
Cloud SQL for MySQLCloud SQL has upgraded Replicating from an external server to version 1.1. You can now:
- Replicate from sources where GTID is not enabled.
- Allow Cloud SQL to copy data directly from an external server to a Cloud SQL replica.
- Use new APIs that give you greater control to verify replication requirements, retry after making external server configuration changes, and remove the 30-minute limit for successful connectivity to an external server.
Cloud SQL for SQL Server enables you to set a default collation value for databases in an instance. This collation value is a default for sorting rules, case, and accent sensitivity. You can set this value through the Cloud Console, the gcloud
command, and the Cloud SQL Admin API.
September 15, 2020
Cloud SQL for MySQLCloud SQL now offers serverless export. With serverless export, Cloud SQL performs the export from a temporary instance. Offloading the export operation allows databases on the primary instance to continue to serve queries and perform other operations at the usual performance rate.
Cloud SQL now offers serverless export. With serverless export, Cloud SQL performs the export from a temporary instance. Offloading the export operation allows databases on the primary instance to continue to serve queries and perform other operations at the usual performance rate.
The following PostgreSQL minor versions have been upgraded:
- PostgreSQL 9.6.16 is upgraded to 9.6.18.
- PostgreSQL 10.11 is upgraded to 10.13.
- PostgreSQL 11.6 is upgraded to 11.8.
- PostgreSQL 12.1 is upgraded to 12.3.
August 31, 2020
Cloud SQL for SQL ServerCloud SQL for SQL Server supports cloning using the Cloud Console, the gcloud
command, and the Cloud SQL Admin API. When you clone an instance, you create an independent copy of the source instance.
August 25, 2020
Cloud SQL for MySQLCloud SQL for MySQL 8.0 is now generally available. If you have not used MySQL 8.0, familiarize yourself with the What is new in MySQL 8.0 and Changes in MySQL 8.0.
For information about the implementation of MySQL 8.0 on Cloud SQL, see the following topics:
- MySQL 8.0 authentication
- Differences between Cloud SQL and standard MySQL functionality
- Unsupported Cloud SQL feature in MySQL 8.0 for Cloud SQL
To get started using MySQL 8.0 on Cloud SQL, see Creating instances.
July 09, 2020
Cloud SQL for PostgreSQLCloud SQL now supports point-in-time recovery (PITR) for PostgreSQL. Point-in-time recovery helps you recover an instance to a specific point in time. For example, if an error causes a loss of data, you can recover a database to its state before the error occurred.
June 23, 2020
Cloud SQL for MySQLCommitted use discounts (CUDs) are now available to purchase for Cloud SQL. CUDs provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. With committed use discounts for Cloud SQL, you can earn a deep discount off your cost of use in exchange for committing to continuously use database instances in a particular region for a 1- or 3-year term. See the documentation for more details.
Committed use discounts (CUDs) are now available to purchase for Cloud SQL. CUDs provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. With committed use discounts for Cloud SQL, you can earn a deep discount off your cost of use in exchange for committing to continuously use database instances in a particular region for a 1- or 3-year term. See the documentation for more details.
Committed use discounts (CUDs) are now available to purchase for Cloud SQL. CUDs provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. With committed use discounts for Cloud SQL, you can earn a deep discount off your cost of use in exchange for committing to continuously use database instances in a particular region for a 1- or 3-year term. See the documentation for more details.
June 08, 2020
Cloud SQL for MySQLSupport for asia-southeast2 region (Jakarta).
Support for asia-southeast2 region (Jakarta).
Support for asia-southeast2 region (Jakarta).
May 21, 2020
Cloud SQL for PostgreSQLPostgreSQL version 12 is now generally available. To start using PostgreSQL 12, see Creating instances.
May 18, 2020
Cloud SQL for MySQLMySQL 5.6 minor version is upgraded to 5.6.42. MySQL 5.7 minor version is upgraded to 5.7.25.
May 15, 2020
Cloud SQL for PostgreSQLPostgreSQL 9.6 minor version is upgraded to 9.6.16. PostgreSQL 10 minor version is upgraded to 10.11. PostgreSQL 11 minor version is upgraded to 11.6. PostgreSQL 12 minor version is upgraded to 12.1.
May 11, 2020
Cloud SQL for PostgreSQLCloud SQL has expanded support for PostgreSQL extensions. Eight additional PostgreSQL extensions are now available:
- pageinspect
- pgfincore
- pg_freespacemap
- pg_repack
- pg_visibility
- PL/Proxy
- postgres_fdw
- postgresql-hll
For information about these newly-added extensions, see PostgreSQL extensions.
May 04, 2020
Cloud SQL for MySQLAs previously announced, Cloud SQL First Generation was deprecated on January 29, 2019. All First Generation instances have been migrated to Second Generation. In the documentation and in the Google Cloud Console, "MySQL Second Generation instances" are now referred to simply as "MySQL instances." For general information about this deprecation, see the existing deprecation notice.
April 20, 2020
Cloud SQL for MySQLSupport for us-west4 region (Las Vegas).
Support for us-west4 region (Las Vegas).
Support for us-west4 region (Las Vegas).
March 27, 2020
Cloud SQL for PostgreSQLPostgreSQL version 12 is now Beta. To start using PostgreSQL 12, see Creating instances.
PostgreSQL version 10 is now generally available. To start using PostgreSQL 10, see Creating instances.
March 24, 2020
Cloud SQL for MySQLCloud SQL now supports 96-core machine types for MySQL, Postgres, and SQL Server instances. For pricing-related information, see the Pricing page.
Cloud SQL now supports 96-core machine types for MySQL, Postgres, and SQL Server instances. For pricing-related information, see the Pricing page.
Cloud SQL now supports 96-core machine types for MySQL, Postgres, and SQL Server instances. For pricing-related information, see the Pricing page.
March 16, 2020
Cloud SQL for MySQLCloud SQL now supports read replicas in a different region than that of the primary instance, providing additional protection against regional outages and improving read performance by making replicas available closer to your application. To get started, see Cross-region replicas.
Cloud SQL instances using private IP are now accessible across regions, at the regular cross-region network egress cost.
Cloud SQL now supports read replicas in a different region than that of the primary instance, providing additional protection against regional outages and improving read performance by making replicas available closer to your application. To get started, see Cross-region replicas.
Cloud SQL instances using private IP are now accessible across regions, at the regular cross-region network egress cost.
Cloud SQL instances using private IP are now accessible across regions, at the regular cross-region network egress cost.
February 27, 2020
Cloud SQL for MySQLMySQL 5.6.42 is now generally available in Cloud SQL. To start using MySQL 5.6.42, see Creating Instances.
February 24, 2020
Cloud SQL for MySQLSupport for us-west3 region (Salt Lake City).
Support for us-west3 region (Salt Lake City).
Support for us-west3 region (Salt Lake City).
February 19, 2020
Cloud SQL for SQL ServerCloud SQL for SQL Server now is generally available. Additionally, Cloud SQL for SQL Server includes new security and performance enhancements. To create SQL Server instances, see Creating Instances.
February 06, 2020
Cloud SQL for MySQLFirst Generation instances no longer can be created. As previously announced, Cloud SQL First Generation was deprecated on January 29, 2019. To improve performance, availability, and storage capacity, Cloud SQL Second Generation has replaced First Generation. For more information, see the existing deprecation notice and, if necessary, the information about upgrading an instance.
January 30, 2020
Cloud SQL for PostgreSQLPostgreSQL version 10 is now Beta. To start using PostgreSQL 10, see Creating Instances.
January 24, 2020
Cloud SQL for MySQLSupport for asia-northeast3 region (Seoul).
Support for asia-northeast3 region (Seoul).
Support for asia-northeast3 region (Seoul).
December 17, 2019
Cloud SQL for MySQLCloud SQL now supports VPC Service Controls, which let you add a service perimeter around the Cloud SQL Admin API and host project for Cloud SQL instances to reduce the risk of data exfiltration. To learn more about using VPC Service Controls with Cloud SQL, see Configuring VPC Service Controls.
Cloud SQL now supports VPC Service Controls, which let you add a service perimeter around the Cloud SQL Admin API and host project for Cloud SQL instances to reduce the risk of data exfiltration. To learn more about using VPC Service Controls with Cloud SQL, see Configuring VPC Service Controls.
Cloud SQL now supports VPC Service Controls, which let you add a service perimeter around the Cloud SQL Admin API and host project for Cloud SQL instances to reduce the risk of data exfiltration. To learn more about using VPC Service Controls with Cloud SQL, see Configuring VPC Service Controls.
December 13, 2019
Cloud SQL for MySQLYou 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.
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.
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 for MySQLCloud 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.
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.
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 for MySQLCloud 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.
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.
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 for MySQLCloud 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).
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).
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 for MySQLCloud 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
Cloud SQL for SQL ServerThe beta version of Cloud SQL for SQL Server is available. To begin creating SQL Server instances, see Creating Instances.
September 27, 2019
Cloud SQL for PostgreSQLPostgreSQL 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
Cloud SQL for MySQLThis 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.
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 for MySQLCloud 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.
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
Cloud SQL for MySQLSupport for asia-northeast2 region (Osaka, Japan).
Support for asia-northeast2 region (Osaka, Japan).
April 09, 2019
Cloud SQL for PostgreSQLCloud SQL now supports PostgreSQL version 11.1 Beta. To start using PostgreSQL 11 Beta, see Creating Instances.
April 03, 2019
Cloud SQL for MySQLSupport added for 122 MySQL flags and 96 PostgreSQL flags. See Supported PostgreSQL Flags and Supported MySQL Flags.
Support added for 122 MySQL flags and 96 PostgreSQL flags. See Supported PostgreSQL Flags and Supported MySQL Flags.
March 11, 2019
Cloud SQL for MySQLSupport for europe-west6 region (Zürich, Switzerland).
Support for europe-west6 region (Zürich, Switzerland).
February 13, 2019
Cloud SQL for PostgreSQLCloud 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 for MySQLCloud SQL Second Generation is replacing First Generation. Support for First Generation instances for MySQL is ending March 25th, 2020.
December 06, 2018
Cloud SQL for MySQLGA support for Private IP connectivity.
GA support for Private IP connectivity.
November 06, 2018
Cloud SQL for PostgreSQLOctober 01, 2018
Cloud SQL for MySQLSupport for asia-east2 region (Hong Kong).
Upgrade to Second Generation generally available for eligible First Generation MySQL instances.
Support for asia-east2 region (Hong Kong).
September 01, 2018
Cloud SQL for MySQLBeta support for private IP (private services access) connectivity.
Proxy version 1.12 released.
Beta support for private IP (private services access) connectivity.
Proxy version 1.12 released.
August 01, 2018
Cloud SQL for PostgreSQLPostGIS extension includes full support for JSON-C.
July 01, 2018
Cloud SQL for MySQLSupport for us-west2 region (Los Angeles).
Support for us-west2 region (Los Angeles).
June 01, 2018
Cloud SQL for MySQLSupport for connecting from Cloud Functions Beta.
Support for europe-north1 region (Finland).
Support for rotating SSL certificates.
Support for connecting from Cloud Functions Beta.
Support for europe-north1 region (Finland).
Support for rotating SSL certificates.
May 01, 2018
Cloud SQL for MySQLSupport for asia-southeast1 region (Singapore).
Support for asia-southeast1 region (Singapore).
April 01, 2018
Cloud SQL for PostgreSQLGA support for Cloud SQL for PostgreSQL.
March 01, 2018
Cloud SQL for MySQLSupport for europe-west4 region (Netherlands).
Support for europe-west4 region (Netherlands).
February 01, 2018
Cloud SQL for MySQLMaximum concurrent connections to App Engine updated from 12 to 60.
Maximum concurrent connections to App Engine updated from 12 to 60.
January 01, 2018
Cloud SQL for MySQLMySQL 5.6 minor version upgraded to 5.6.36.
Support for northamerica-northeast1 region (Montréal).
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 01, 2017
Cloud SQL for MySQLBeta support for the high availability configuration and replication for PostgreSQL instances.
Beta support for the high availability configuration and replication for PostgreSQL instances.
October 01, 2017
Cloud SQL for MySQLSupport for asia-south1 region (Mumbai).
Proxy version 1.11 released.
Support for asia-south1 region (Mumbai).
Proxy version 1.11 released.
September 01, 2017
Cloud SQL for MySQLSupport for 64-core machine types for MySQL instances and 64 cores for PostgreSQL instances.
Support for southamerica-east1 region (São Paulo).
Support for 64-core machine types for MySQL instances and 64 cores for PostgreSQL instances.
Support for southamerica-east1 region (São Paulo).
August 01, 2017
Cloud SQL for MySQLSupport for europe-west3 region (Frankfurt).
Support for europe-west3 region (Frankfurt).
June 01, 2017
Cloud SQL for MySQLSupport for labels.
Proxy version 1.10 released.
Support for australia-southeast1 region (Sydney).
Support for europe-west2 region (London).
Support for labels.
Proxy version 1.10 released.
Support for the JDBC Socket Library for PostgreSQL.
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 01, 2017
Cloud SQL for MySQLGA 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).
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 01, 2017
Cloud SQL for MySQLProxy version 1.09 released.
Proxy version 1.09 released.
March 01, 2017
Cloud SQL for MySQLSupport for 32-core machine types for MySQL instances.
Support for making MySQL general and slow query log files available through the Stackdriver Log Viewer.
Cloud SQL for PostgreSQL Beta availability.
To provide feedback on the beta release, go to our Cloud SQL user forum.
February 01, 2017
Cloud SQL for MySQLSupport for Identity and Access Management (IAM) predefined roles.
December 01, 2016
Cloud SQL for MySQLSupport for administration of users and databases for Second Generation instances in the Google Cloud Console and the Cloud SQL API.
November 01, 2016
Cloud SQL for MySQLSupport for Northeastern Asia Pacific region (asia-northeast1
).
MySQL 5.7 minor version upgraded to 5.7.14.
August 01, 2016
Cloud SQL for MySQLCloud SQL Second Generation General Availability.
- Up to 16 cores and 104 GB RAM.
- SSD or HDD storage option with optional automatic storage increase capability.
- Optional high availability configuration (recommended for all production instances).
- Configurable maintenance window and maintenance timing.
- MySQL compatibility:
- MySQL 5.6 (5.6.31) and 5.7 (5.7.11)
- InnoDB storage engine
- GTID support