Cloud SQL release notes

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.

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.

November 04, 2024

Cloud SQL for MySQL

You can now view the size of a backup for a Cloud SQL instance.

Cloud SQL for PostgreSQL

You can now view the size of a backup for a Cloud SQL instance.

Cloud SQL for SQL Server

You can now view the size of a backup for a Cloud SQL instance.

October 25, 2024

Cloud SQL for MySQL

When you run the backupRuns.GET API or the gcloud sql backups describe command, the maxChargeableBytes parameter now appears in the response. This parameter contains the maximum number of bytes that you can be charged for a backup.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

October 23, 2024

Cloud SQL for PostgreSQL

PostgreSQL version 17 is now generally available.

When using the CLI/API to create an instance, if the database version for the instance or replica that you're creating is PostgreSQL 16 and later, then the default Cloud SQL edition is Enterprise Plus.

When using the CLI/API to create an instance, If you either don't specify a database version or you specify a version other than PostgreSQL 16 and later, then the default Cloud SQL edition is Enterprise.

The following information applies to flags and extensions for PostgreSQL 17:

Flags

These flags are deprecated for PostgreSQL 17:

old_snapshot_threshold
trace_recovery_messages

For more information, see Configure database flags.

Extensions

Cloud SQL for PostgreSQL version 17 doesn't support these extensions:

ip4r
oracle_fdw
orafce
pg_background
pg_bigm
pgfincore
pg_hint_plan
pg_partman
pg_proctab
pgrouting
pg_similarity
pg_squeeze
pgtap
pgtt
pg_wait_sampling
PL/Proxy
plv8
postgresql_anonymizer
postgresql_hll
prefix
rdkit
temporal_tables

To start using PostgreSQL 17, see Create instances.

October 21, 2024

Cloud SQL for MySQL

You can now create a read replica for an instance that has private services access configured for it and connector enforcement enabled for it. For more information, see Connect using Cloud SQL Language Connectors.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

October 16, 2024

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.39. To upgrade your existing MySQL 8.0 instance to the new version, see Upgrade the database minor version.

October 09, 2024

Cloud SQL for SQL Server

Cloud SQL configures the max server memory (mb) flag based on the instance size automatically by limiting the amount of memory that SQL Server can allocate for its internal pools. For more information, see Configure database flags.

You can export the transaction logs for point-in-time recovery (PITR) that Cloud SQL stores in Cloud Storage. This feature is in Preview.

October 03, 2024

Cloud SQL for MySQL

You can now configure server certificate authority (CA) mode when you create a Cloud SQL instance. With server CA mode, you have two options:

Per-instance CA: this is the default configuration. With this option, an internal CA dedicated to each Cloud SQL instance signs the server certificate for that instance.
Shared CA: with this option, the Cloud SQL instance uses a CA hierarchy consisting of a root CA and subordinate server CAs managed by Cloud SQL and hosted on Google Cloud Certificate Authority Service (CA Service). The subordinate server CAs in a region sign the server certificates and are shared across instances in the region. This option can be used only with MySQL 8.0.30 and later.

For more information about each option, see Certificate authority (CA) hierarchies. This feature is in Preview.

Cloud SQL for PostgreSQL

The pg_ivm extension, version 1.9, is generally available. This extension enables you to make materialized views up-to-date in which only incremental changes are computed and applied on views rather than recomputing the contents from scratch.

Cloud SQL for PostgreSQL, version 16, now supports the pgRouting extension. This extension extends PostGIS and enhances geospatial processing through network routing and analysis.

For more information on these extensions, see Configure PostgreSQL extensions.

The rollout of the following minor versions, extension versions, and plugin versions is underway:

Minor versions

12.19 is upgraded to 12.20.
13.15 is upgraded to 13.16.
14.12 is upgraded to 14.13.
15.7 is upgraded to 15.8.
16.3 is upgraded to 16.4.

Extension and plugin versions

google_ml_integration is upgraded from 1.2 to 1.4.2.
pgvector is upgraded from 0.7.0 to 0.7.4.

If you use a maintenance window, then the updates to the minor, extension, and plugin versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks.

The new maintenance version is [PostgreSQL version].R20240910.01.00_02. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

You can now configure server certificate authority (CA) mode when you create a Cloud SQL instance. With server CA mode, you have two options:

Per-instance CA: this is the default configuration. With this option, an internal CA dedicated to each Cloud SQL instance signs the server certificate for that instance.
Shared CA: with this option, the Cloud SQL instance uses a CA hierarchy consisting of a root CA and subordinate server CAs managed by Cloud SQL and hosted on Google Cloud Certificate Authority Service (CA Service). The subordinate server CAs in a region sign the server certificates and are shared across instances in the region.

For more information about each option, see Certificate authority (CA) hierarchies. This feature is in Preview.

Cloud SQL for SQL Server

You can now configure server certificate authority (CA) mode when you create a Cloud SQL instance. With server CA mode, you have two options:

Per-instance CA: this is the default configuration. With this option, an internal CA dedicated to each Cloud SQL instance signs the server certificate for that instance.
Shared CA: with this option, the Cloud SQL instance uses a CA hierarchy consisting of a root CA and subordinate server CAs managed by Cloud SQL and hosted on Google Cloud Certificate Authority Service (CA Service). The subordinate server CAs in a region sign the server certificates and are shared across instances in the region.

For more information about each option, see Certificate authority (CA) hierarchies. This feature is in Preview.

October 01, 2024

Cloud SQL for MySQL

Cloud SQL for MySQL 8.4 is now generally available. For more information about the differences between MySQL 8.4 and MySQL 8.0, review What Is New in MySQL 8.4 since MySQL 8.0.

By default, if you specify MySQL 8.4 as the version when you create a Cloud SQL instance (either primary or replica) using the gcloud CLI or the REST API, then the Cloud SQL edition is Enterprise Plus.

If you specify a version other than MySQL 8.4 or don't specify a version, then the default Cloud SQL edition of the instance is Enterprise.

For more information about the implementation of MySQL 8.4 in Cloud SQL, see the following topics:

To create a MySQL 8.4 instance in Cloud SQL, see Create instances. Before you upgrade to MySQL 8.4, you must first upgrade to MySQL 8.0.37 or later. To perform a major version upgrade, see Upgrade the database major version in-place. To perform a minor version upgrade of Cloud SQL for MySQL 8.0, see Upgrade the database minor version.

Cloud SQL for SQL Server

You can now use the gcloud sql instances patch command to update the time zone of your Cloud SQL for SQL Server instance after you create the instance. Previously, you could only set a custom time zone for a SQL Server instance when you first created the instance. For more information about setting the time zone for a Cloud SQL for SQL Server instance, see About instance settings.

September 25, 2024

Cloud SQL for PostgreSQL

You can now set up AlloyDB free trial clusters using a copy of your Cloud SQL for PostgreSQL backup. For more information, see Migrate from Cloud SQL for PostgreSQL to AlloyDB.

September 19, 2024

Cloud SQL for PostgreSQL

You can now use gcloud or the Cloud SQL Admin API to switch the storage location of the transaction logs used for point-in-time recovery on your instance without downtime to Cloud Storage. For more information, see Use point-in-time recovery and Switch transaction log storage to Cloud Storage.

September 16, 2024

Cloud SQL for MySQL

Cloud SQL is discontinuing support for legacy high availability (HA) instance configuration on January 6, 2025. After this date, you can't create Cloud SQL for MySQL instances with the legacy configuration for high availability. You also can't enable the legacy configuration for high availability on existing instances. Until January 6, 2025, legacy HA instances are still covered by the Cloud SQL SLA. We recommend that you upgrade your existing legacy HA instances to regional persistent disk HA instances as soon as possible and create new HA instances using regional persistent disk instead.

Starting on May 1, 2025, Cloud SQL will migrate any remaining instances that use the legacy HA configuration to the current HA configuration automatically.

September 13, 2024

Cloud SQL for SQL Server

For Cloud SQL Enterprise Plus edition, you can set the number of days of retained transaction logs from 1 to 35. For more information, see Use point-in-time recovery (PITR).

September 12, 2024

Cloud SQL for MySQL

Cloud SQL now supports near-zero downtime planned maintenance on standalone Cloud SQL Enterprise Plus edition primary instances. In addition, you can also simulate near-zero downtime for planned maintenance events on standalone Cloud SQL Enterprise Plus edition primary instances.

For more information, see About maintenance on Cloud SQL instances.

You can now upgrade your instances to Cloud SQL Enterprise Plus edition with near-zero downtime. To upgrade your instance, see Upgrade an instance to Cloud SQL Enterprise Plus edition using in-place upgrade.

You can now upgrade the minor version of a Cloud SQL for MySQL Enterprise Plus edition instance with near-zero downtime. To upgrade the minor version of your Cloud SQL for MySQL 8.0 instance, see Upgrade the minor version.

You can now provide access to Cloud SQL Studio by granting a new IAM role, Cloud SQL Studio User (roles/cloudsql.studioUser), instead of using the Cloud SQL Admin IAM role.

For more information about using Cloud SQL Studio, see Manage your data using Cloud SQL Studio.

Cloud SQL for PostgreSQL

For more information, see About maintenance on Cloud SQL instances.

You can now provide access to Cloud SQL Studio by granting a new IAM role, Cloud SQL Studio User (roles/cloudsql.studioUser), instead of using the Cloud SQL Admin IAM role.

For more information about using Cloud SQL Studio, see Manage your data using Cloud SQL Studio.

Cloud SQL for SQL Server

You can now provide access to Cloud SQL Studio by granting a new IAM role, Cloud SQL Studio User (roles/cloudsql.studioUser), instead of using the Cloud SQL Admin IAM role.

For more information about using Cloud SQL Studio, see Manage your data using Cloud SQL Studio.

September 03, 2024

Cloud SQL for MySQL

When you clone your zonal instance, you can now specify a preferred zone for the instance. You can also specify preferred primary and secondary zones for your regional instance. If the zones for your instance go down in the future, then Cloud SQL can assign the preferred zones to the instance, and you don't experience downtime. For more information, see Clone instances.

Cloud SQL for PostgreSQL

You can now use point-in-time recovery to restore your zonal instance to a preferred primary zone and your regional instance to both a preferred primary zone and a preferred secondary zone. For more information, see Use point-in-time recovery (PITR).

Cloud SQL for SQL Server

August 15, 2024

Cloud SQL for MySQL

Extended support pricing is now available for Cloud SQL for MySQL. To view pricing details, see Cloud SQL pricing.

For more information about extended support, see Extended support for Cloud SQL.

For more information about extended support timelines, see Database versions and version policies.

Cloud SQL for PostgreSQL

Extended support pricing is now available for Cloud SQL for PostgreSQL. To view pricing details, see Cloud SQL pricing.

For more information about extended support, see Extended support for Cloud SQL.

For more information about extended support timelines, see Database versions and version policies.

If your Cloud SQL Enterprise edition instance stores the transaction logs used for point-in-time recovery (PITR) on disk, then when you do an in-place upgrade to Cloud SQL Enterprise Plus edition the storage location for the transaction logs is switched to Cloud Storage. For more information, see Upgrade an instance to Cloud SQL Enterprise Plus edition by using in-place upgrade.

To check where your instance stores the transaction logs used for PITR, see Use point-in-time recovery (PITR).

August 01, 2024

Cloud SQL for SQL Server

Cloud SQL for SQL Server now offers two editions of Cloud SQL to support your various business and application needs: Cloud SQL Enterprise Plus edition and Cloud SQL Enterprise edition. Each edition provides different performance and availability characteristics to meet the needs of your applications.

Cloud SQL Enterprise Plus edition has new machines for better performance, higher availability, and advanced disaster recovery. Existing instances become Cloud SQL Enterprise edition for SQL Server instances with no changes to pricing or features. You can upgrade existing instances to the Cloud SQL Enterprise Plus edition in-place using the Google Cloud Console, the gcloud CLI, or the API with minimal downtime.

For more information about Cloud SQL editions, see Introduction to Cloud SQL editions.

July 31, 2024

Cloud SQL for MySQL

Gemini in Databases assistance in Cloud SQL for MySQL is now available in Preview for query insights, system insights, index advisor, and active queries. You can use Gemini assistance to help you observe and troubleshoot your Cloud SQL resources. For more information, see Observe and troubleshoot with Gemini assistance.

Cloud SQL for PostgreSQL

Gemini in Databases assistance in Cloud SQL for PostgreSQL is now available in Preview for query insights, system insights, index advisor, and active queries. You can use Gemini assistance to help you observe and troubleshoot your Cloud SQL resources. For more information, see Observe and troubleshoot with Gemini assistance.

July 30, 2024

Cloud SQL for MySQL

You can now use the gcloud CLI or the Cloud SQL Admin API to switch the storage location of transaction logs used for point-in-time recovery (PITR) on your instance from disk to Cloud Storage. For more information, see Use point-in-time recovery and Switch transaction log storage to Cloud Storage.

July 29, 2024

Cloud SQL for MySQL

Migrating your external MySQL 5.7 and 8.0 databases into Cloud SQL for MySQL by using Percona XtraBackup physical files is now generally available (GA).

For more information, see Migrate to Cloud SQL from an XtraBackup physical file.

July 26, 2024

Cloud SQL for MySQL

IAM group authentication is now generally available (GA) for Cloud SQL for MySQL. You can add IAM groups to Cloud SQL instances and manage database access at the group level. To use IAM group authentication, you must have [MySQL version].R20230909.02_00 or later installed on your instance.

Cloud SQL for PostgreSQL

IAM group authentication is now generally available (GA) for Cloud SQL for PostgreSQL. You can add IAM groups to Cloud SQL instances and manage database access at the group level. To use IAM group authentication, you must have [PostgreSQL version].R20240514.00_04 or later installed on your instance.

Migrate to AlloyDB insight recommendations are available in Preview.

July 25, 2024

Cloud SQL for MySQL

You can now upgrade the network architecture of a Cloud SQL instance that isn't enabled with high-availability. The previous limitation on upgrading the network architecture of these instances is removed. To check whether your Cloud SQL instance has high availability enabled, see Verify an instance's high availability configuration.

For more information about upgrading your network architecture, see Upgrade an instance to the new network architecture.

Cloud SQL for PostgreSQL

For more information about upgrading your network architecture, see Upgrade an instance to the new network architecture.

Cloud SQL for SQL Server

For more information about upgrading your network architecture, see Upgrade an instance to the new network architecture.

July 19, 2024

Cloud SQL for SQL Server

You can now use Extended Events (XEvents) on your Cloud SQL for SQL Server instance to monitor, identify, and troubleshoot the performance of the databases on your instance.

July 18, 2024

Cloud SQL for MySQL

You can now create custom organization policies for Cloud SQL instances. For more information, see Add custom organization policies.

Cloud SQL for PostgreSQL

You can now create custom organization policies for Cloud SQL instances. For more information, see Add custom organization policies.

Cloud SQL for SQL Server

You can now create custom organization policies for Cloud SQL instances. For more information, see Add custom organization policies.

July 17, 2024

Cloud SQL for PostgreSQL

You can now use the following optional flags when you export and import files into Cloud SQL instances:

--clean: if you export files, then this flag enables you to include the DROP <object> SQL statement that's required to drop (clean) database objects before you import them. If you import files, then this flag enables you to clean database objects before you recreate them.
--if-exists: this flag enables you to include the IF EXISTS SQL statement with each DROP statement that's produced by the clean flag.

If you import files, then these flags apply only if you use the --parallel flag. If you export files, then use these flags only if you're not exporting files in parallel.

July 16, 2024

Cloud SQL for MySQL

Cloud SQL Studio is now generally available. For more information, see Manage your data using Cloud SQL Studio.

You can now search for and manage your Cloud SQL resources by using Dataplex Catalog. For more information about the integration of Cloud SQL and Dataplex Catalog, see Manage your Cloud SQL resources using Dataplex Catalog.

Cloud SQL for PostgreSQL

Cloud SQL Studio is now generally available. For more information, see Manage your data using Cloud SQL Studio.

Cloud SQL for SQL Server

Cloud SQL Studio is now generally available. For more information, see Manage your data using Cloud SQL Studio.

July 02, 2024

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition now supports the southamerica-west1 (Santiago) region.

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports the southamerica-west1 (Santiago) region.

June 24, 2024

Cloud SQL for MySQL

You can now upgrade the network architecture of Cloud SQL for MySQL instances that store transaction logs used for point-in-time recovery (PITR) in Cloud Storage. The previous limitation on upgrade of such instances is removed. To check where your MySQL instance stores its PITR logs, see Check the storage location of transaction logs used for PITR.

For more information about upgrading your network architecture, see Upgrade an instance to the new network architecture.

June 21, 2024

Cloud SQL for PostgreSQL

You can now use the in-place major version upgrade feature to upgrade your Cloud SQL for PostgreSQL instance to PostgreSQL 16.

June 20, 2024

Cloud SQL for MySQL

You can now use the gcloud sql instances describe command or the SQL Admin API to retrieve a list of database versions that are available to your MySQL instance for upgrade. For more information, see Plan a major version upgrade and Upgrade the database minor version.

Cloud SQL for PostgreSQL

You can now use the gcloud sql instances describe command or the SQL Admin API to retrieve a list of database versions that are available to your PostgreSQL instance for upgrade. For more information, see Plan a major version upgrade.

Cloud SQL for SQL Server

You can now use the gcloud sql instances describe command or the SQL Admin API to retrieve a list of database versions that are available to your SQL Server instance for upgrade. For more information, see Plan a major version upgrade.

June 13, 2024

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.37. To upgrade your existing instance to the new version, see Upgrade the database minor version.

June 10, 2024

Cloud SQL for MySQL

You can now choose to receive a maintenance notification 5 weeks before the maintenance update of your Cloud SQL instance is scheduled to occur. This option is named Week 5.

In addition, some labels in the Google Cloud Console have been renamed to align with this new option:

Order of update is renamed to Maintenance timing
Earlier is renamed to Week 1
Later is renamed to Week 2

For more information, see Maintenance settings and Find and set maintenance windows.

Cloud SQL for PostgreSQL

The temporal_tables extension, version 1.2.2 is generally available. This extension provides support for temporal tables. A temporal table records the period of time when a row is valid from a database perspective. For more information, see Configure PostgreSQL extensions.

You can now perform CREATE CAST and DROP CAST statements as a database user with the cloudsqlsuperuser role. For more information, see About PostgreSQL users and roles.

The rollout of the following minor versions, extension versions, and plugin versions is underway:

Minor versions

12.17 is upgraded to 12.19.
13.13 is upgraded to 13.15.
14.10 is upgraded to 14.12.
15.5 is upgraded to 15.7.

Extension and plugin versions

google_ml_integration is upgraded from 1.2 to 1.3.
pg_partman is upgraded from 4.7.4 to 5.0.1 (for PostgreSQL versions 14 and later).
pgvector is upgraded from 0.6.0 to 0.7.0.
Plv8 is upgraded from 3.2.0 to 3.2.2.
PostGIS is upgraded from 3.2.5 to 3.4.0 (for PostgreSQL versions 12 and later).

The new maintenance version is [PostgreSQL version].R20240514.00_04. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

You can now choose to receive a maintenance notification 5 weeks before the maintenance update of your Cloud SQL instance is scheduled to occur. This option is named Week 5.

In addition, some labels in the Google Cloud Console have been renamed to align with this new option:

Order of update is renamed to Maintenance timing
Earlier is renamed to Week 1
Later is renamed to Week 2

For more information, see Maintenance settings and Find and set maintenance windows.

Cloud SQL for SQL Server

You can now choose to receive a maintenance notification 5 weeks before the maintenance update of your Cloud SQL instance is scheduled to occur. This option is named Week 5.

In addition, some labels in the Google Cloud Console have been renamed to align with this new option:

Order of update is renamed to Maintenance timing
Earlier is renamed to Week 1
Later is renamed to Week 2

For more information, see Maintenance settings and Find and set maintenance windows.

June 07, 2024

Cloud SQL for PostgreSQL

PostgreSQL version 16 is now generally available.

When you use gcloud or the API to create an instance or replica, the following conditions now apply:

If the database version for the instance or replica that you're creating is PostgreSQL 16, then the default Cloud SQL edition is Enterprise Plus.
If you either don't specify a database version or you specify a version other than PostgreSQL 16, then the default Cloud SQL edition is Enterprise.

You can't use the in place major version upgrade feature to upgrade your Cloud SQL for PostgreSQL instance to PostgreSQL 16.

To start using PostgreSQL 16, see Create instances.

May 31, 2024

Cloud SQL for SQL Server

Cloud SQL for SQL Server now supports storage of point-in-time recovery (PITR) transaction logs in Cloud Storage.

May 29, 2024

Cloud SQL for MySQL

Cloud SQL for MySQL major versions that have reached community end-of-life (EOL) will receive extended support starting on February 1, 2025. For more information about extended support, see Extended support for Cloud SQL.

For more information about extended support timelines, see Database versions and version policies.

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL major versions that have reached community end-of-life (EOL) will receive extended support starting on February 1, 2025. For more information about extended support, see Extended support for Cloud SQL.

For more information about extended support timelines, see Database versions and version policies.

May 23, 2024

Cloud SQL for PostgreSQL

Monitoring active queries in Cloud SQL for PostgreSQL, which is part of the Gemini in Databases Preview, is temporarily unavailable. You can still monitor completed queries. For more information about monitoring queries, see Use Query Insights to improve query performance.

April 22, 2024

Cloud SQL for PostgreSQL

The pgvector extension is upgraded from version 0.5.1 to version 0.6.0. Use this extension to store and search for vector embeddings in PostgreSQL databases. For more information, see Configure PostgreSQL extensions.

To use this version of the extension, update your instance to [PostgreSQL version].R20240130.00_09. For more information, see Self-service maintenance.

April 09, 2024

Cloud SQL for MySQL

The following Gemini in Databases features are now available in Public Preview:

Database Center: an AI-assisted dashboard that gives you one centralized view across your entire database fleet.
Cloud SQL Studio: lets authorized users interact directly with the SQL database and run SQL queries from the Google Cloud console to access and manipulate data.
Monitor active queries: monitor and troubleshoot the queries that are active in your database.
Index advisor: a fully managed index advisor that tracks the queries your database handles regularly.
4-week query metric retention in the Query Insights dashboard.
17 new database insight recommendations.

To learn how to enable and activate Gemini in Databases, see Set up Gemini in Databases.

Cloud SQL for MySQL now supports the storage of vector embeddings in MySQL 8.0.36 and later databases. To use this feature, update your instance to MySQL 8.0.36.R20240401.03_00 or later.

After you store vector embeddings in your database, you can then perform K-nearest neighbor (KNN) searches on the dataset along with the rest of your data. Cloud SQL for MySQL also supports the creation of vector search indexes for several different index types using approximate nearest neighbor (ANN) search.

For more information, see Working with vector embeddings using Cloud SQL for MySQL. This feature is in Preview.

Cloud SQL for PostgreSQL

The following Gemini in Databases features are now available in Public Preview:

Database Center: an AI-assisted dashboard that gives you one centralized view across your entire database fleet.
Cloud SQL Studio: lets authorized users interact directly with the SQL database and run SQL queries from the Google Cloud console to access and manipulate data.
Monitor active queries: monitor and troubleshoot the queries that are active in your database.
Index advisor: a fully managed index advisor that tracks the queries your database handles regularly.
4-week query metric retention in the Query Insights dashboard.
15 new database insight recommendations.

To learn how to enable and activate Gemini in Databases, see Set up Gemini in Databases.

Cloud SQL for SQL Server

The following Gemini in Databases features are now available in Public Preview:

Database Center: an AI-assisted dashboard that gives you one centralized view across your entire database fleet.
Cloud SQL Studio: lets authorized users interact directly with the SQL database and run SQL queries from the Google Cloud console to access and manipulate data.
9 new database insight recommendations.

To learn how to enable and activate Gemini in Databases, see Set up Gemini in Databases.

April 08, 2024

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition primary instances with high availability (HA) now require less than one second of downtime for planned maintenance.

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition primary instances with high availability (HA) now require less than one second of downtime for planned maintenance.

April 04, 2024

Cloud SQL for MySQL

For Cloud SQL Enterprise Plus edition, you can now use advanced disaster recovery (DR) to simplify recovery and fallback processes after you perform a cross-regional failover. With advanced DR, you can:

Designate a cross-region disaster recovery (DR) replica
Perform replica failover
Restore your original deployment by using zero data loss switchover

You can also use switchover to simulate disaster recovery without data loss.

For more information, see Advanced disaster recovery (DR) and Use advanced disaster recovery (DR). This feature is in Preview.

April 03, 2024

Cloud SQL for MySQL

You can now migrate your external MySQL 5.7 and 8.0 databases into Cloud SQL for MySQL by using Percona XtraBackup physical files. This feature is in Preview.

For more information, see Migrate to Cloud SQL from an XtraBackup physical file.

Cloud SQL for PostgreSQL

You can now migrate data in the tables of your database in parallel. There's a performance improvement because Cloud SQL can transfer the data with parallel processes within a database. You can set the speed that Cloud SQL transfers this data to min, optimal, or max.

April 02, 2024

Cloud SQL for MySQL

You can now scale up the compute size (vCPU, memory) of a Cloud SQL Enterprise Plus edition primary instance with near-zero downtime.

Cloud SQL for PostgreSQL

Version 0.6.0 of the pgvector extension that's listed in the March 27 release note isn't available yet. Use version 0.5.1 of this extension.

You can now scale up the compute size (vCPU, memory) of a Cloud SQL Enterprise Plus edition primary instance with near-zero downtime.

Cloud SQL for SQL Server

You can now use SSL mode instead of the legacy require_ssl setting to specify the encryption requirements for connections to your Cloud SQL for SQL Server instances. For more information, see Enforce SSL/TLS encryption.

April 01, 2024

Cloud SQL for MySQL

If your Cloud SQL Enterprise edition instance stores the transaction logs used for point-in-time recovery (PITR) on disk, then when you do an in-place upgrade to Cloud SQL Enterprise Plus edition, the storage location for the transaction logs is switched to Cloud Storage. For more information, see Upgrade an instance to Cloud SQL Enterprise Plus edition by using in-place upgrade.

To check where your instance stores the transaction logs used for PITR, see Use point-in-time recovery (PITR)

March 28, 2024

Cloud SQL for MySQL

You can now simulate a planned maintenance update with near-zero downtime on your Cloud SQL Enterprise Plus primary instance without updating your database. For more information, see About maintenance on Cloud SQL instances.

Cloud SQL for PostgreSQL

March 27, 2024

Cloud SQL for PostgreSQL

To use this version of the extension, update your instance to [PostgreSQL version].R20240130.00_07. For more information, see Self-service maintenance.

The rollout of the following items in the February 7 release note is now complete:

Extensions
Flags
Minor versions
Extension versions
Plugin versions

March 26, 2024

Cloud SQL for PostgreSQL

You can now integrate Cloud SQL and Vertex AI. This integration lets you apply large language models (LLMs), which are hosted in Vertex AI, to a Cloud SQL for PostgreSQL database, version 12 and later. For more information, see Integrate Cloud SQL with Vertex AI.

March 25, 2024

Cloud SQL for MySQL

Private Service Connect now includes support for cross-region read replicas. You can also choose an availability type (REGIONAL or ZONAL) for Private Service Connect-enabled instances. Both features are in GA.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

You can now use Private Service Connect to connect to a Cloud SQL for SQL Server instance. This solution allows you to connect to the instance from multiple VPC networks that belong to different groups, teams, projects, or organizations.

Private Service Connect includes support for cross-region read replicas. You can also choose an availability type (REGIONAL or ZONAL) for Private Service Connect-enabled instances.

All features are in GA.

March 19, 2024

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition now supports the me-central2 (Dammam) region.

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports the me-central2 (Dammam) region.

March 14, 2024

Cloud SQL for SQL Server

A new maintenance version rollout is currently underway for all supported SQL Server versions.

Cloud SQL for MySQL

A new maintenance version rollout is currently underway for all supported MySQL versions.

To learn how to check your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

In the new maintenance version [MySQL version].R20240207.00_00, the default value of the performance_schema flag for all MySQL 8.0 instances with more than 15 GB of RAM will be set to on. Previously, the default of on for MySQL 8.0 only applied to 8.0.26 and later. This change applies to new and existing MySQL 8.0 instances. For more information about this flag, see supported flags.

February 09, 2024

Cloud SQL for MySQL

Cloud SQL now automatically updates your read replicas when you perform self-service maintenance on the primary instance. For more information, see Self-service maintenance.

Cloud SQL for PostgreSQL

Cloud SQL now automatically updates your read replicas when you perform self-service maintenance on the primary instance. For more information, see Self-service maintenance.

Cloud SQL for SQL Server

Cloud SQL now automatically updates your read replicas when you perform self-service maintenance on the primary instance. For more information, see Self-service maintenance.

February 08, 2024

Cloud SQL for MySQL

Cloud SQL now supports near-zero downtime planned maintenance on HA-enabled Cloud SQL Enterprise Plus instances with all combinations of public IP connectivity.

Cloud SQL for PostgreSQL

Cloud SQL now supports near-zero downtime planned maintenance on HA-enabled Cloud SQL Enterprise Plus instances with all combinations of public IP connectivity.

February 07, 2024

Cloud SQL for PostgreSQL

The rollout of the following extensions and flags is underway:

Extensions

autoinc (version 1.0): provides functions for incrementing fields automatically. This trigger stores the next value of a sequence into an integer field.
bloom (version 1.0): provides a method to access indexes based on bloom filters. These filters are space-efficient data structures that you can use to test whether an element is a member of a set.
insert_username (version 1.0): provides functions for storing the current user's name into a text field. You can use this to track who last modified a row in a database table.
moddatetime (version 1.0): provides functions for storing the current time into a timestamp field. You can use this to track the last time that a row in a database table is modified.
pg_background (version 1.2): lets you run arbitrary commands in a background worker.
pg_squeeze (version 1.5): removes unused space from a table and lets you use an index to sort records or rows (tuples) of the table.
tcn (version 1.0): provides a trigger function that notifies listeners of changes to the content of database tables.

Flags

cloudsql.enable_pg_squeeze: enables the pg_squeeze extension for Cloud SQL for PostgreSQL
squeeze.max_xlock_time: sets the time (in milliseconds) that the extension uses to finalize the processing for modifying a table
squeeze.worker_autostart: starts a background worker automatically
squeeze.worker_role: specifies the role for the background worker

The rollout of the following minor versions, extension versions, and plugin versions is underway:

Minor versions

11.21 is upgraded to 11.22.
12.16 is upgraded to 12.17.
13.12 is upgraded to 13.13.
14.9 is upgraded to 14.10.
15.4 is upgraded to 15.5.

Extension and plugin versions

ipr4 is upgraded from 2.4.1 to 2.4.2.
orafce is upgraded, as follows:
- from 3.25.1 to 4.6.1 (for PostgreSQL versions 9.6 and 10)
- from 4.6.1 to 4.7.0 (for PostgreSQL versions 11 and later)
pg_cron is upgraded from 1.5.2 to 1.6.0.
pgfincore is upgraded from 1.2.3 to 1.3.1.
pg_partman is upgraded from 4.7.3 to 4.7.4.
pg_repack is upgraded from 1.4.8 to 1.5.0.
pgTAP is upgraded from 1.2.0 to 1.3.0.
pgtt is upgraded from 2.9.0 to 3.0.
pg_wait_sampling is upgraded from 1.1.4 to 1.1.5.
PL/Proxy is upgraded from 2.10.0 to 2.11.0.
plv8 is upgraded from 3.1.4 to 3.2.0.
postgresql_hll is upgraded from 2.17 to 2.18.

The new maintenance version is [PostgreSQL version].R20240130.00_00. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

February 06, 2024

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.36. To upgrade your existing instance to the new version, see Upgrade the database minor version.

February 01, 2024

Cloud SQL for MySQL

For more information, see Connect to an instance using Private Service Connect.

Cloud SQL for PostgreSQL

For more information, see Connect to an instance using Private Service Connect.

Cloud SQL for SQL Server

You can also choose an availability type (REGIONAL or ZONAL) for Private Service Connect-enabled instances.

All features are in Preview. For more information, see Connect to an instance using Private Service Connect.

January 31, 2024

Cloud SQL for MySQL

Support for africa-south1 (Johannesburg) region.

Cloud SQL for PostgreSQL

Support for africa-south1 (Johannesburg) region.

Cloud SQL for SQL Server

Support for africa-south1 (Johannesburg) region.

January 30, 2024

Cloud SQL for MySQL

You can now use the MySQL Shell dumpInstance and loadDump utilities to export and import data for multiple files in parallel. For more information, see Export and import files in parallel.

Cloud SQL for PostgreSQL

You can now use the pg_dump and pg_restore utilities to export and import data for multiple files in parallel. For more information, see Export and import files in parallel.

January 25, 2024

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition now supports the following regions:

asia-northeast2 (Osaka)
asia-south2 (Delhi)
europe-north1 (Finland)
europe-southwest1 (Madrid)
us-east5 (Columbus)
us-south1 (Dallas)

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports the following regions:

asia-northeast2 (Osaka)
asia-south2 (Delhi)
europe-north1 (Finland)
europe-southwest1 (Madrid)
us-east5 (Columbus)
us-south1 (Dallas)

January 12, 2024

Cloud SQL for MySQL

Cloud SQL for MySQL now supports setting microsecond time periods for the following flag on MySQL 5.7 and MySQL 8.0:

innodb_flush_log_at_timeout

For more information about this flag, see supported flags.

December 19, 2023

Cloud SQL for MySQL

You can now specify the SSL mode of your Cloud SQL for MySQL instances. To use SSL mode, you must use maintenance version [MySQL version].R20230909.02_00 or later. For more information, see Enforce SSL/TLS encryption.

December 18, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL has completed the upgrade to MySQL 5.7.44.

Cloud SQL for MySQL now supports the following flags for MySQL 8.0:

innodb_buffer_pool_dump_now
innodb_buffer_pool_load_abort
innodb_buffer_pool_load_now

For more information about these flags, see supported flags.

Cloud SQL Enterprise Plus edition now supports the following regions:

europe-west8 (Milan)
europe-west12 (Turin)
us-west4 (Las Vegas)

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports the following regions:

europe-west8 (Milan)
europe-west12 (Turin)
us-west4 (Las Vegas)

December 14, 2023

Cloud SQL for MySQL

You can now use Database Migration Service to migrate data to an existing Cloud SQL instance that was created using Terraform or other Infrastructure-As-Code (IaC) Tools.

Cloud SQL for PostgreSQL

You can now use Database Migration Service to migrate data to an existing Cloud SQL instance that was created using Terraform or other Infrastructure-As-Code (IaC) Tools.

December 13, 2023

Cloud SQL for MySQL

You can now use the cloudsql_ignore_innodb_encryption flag to ignore InnoDB table encryption when you migrate instances to Cloud SQL. The flag is supported in MySQL 8.0 for Cloud SQL. For more information, see Supported flags.

Cloud SQL for PostgreSQL

The following flags are generally available:

autovacuum_vacuum_insert_scale_factor: specify a fraction of the size of a database table to add to the autovacuum_vacuum_insert_threshold flag. Use this flag when you're deciding whether to run a VACUUM.
autovacuum_vacuum_insert_threshold: specify the minimum number of inserted records or rows (tuples) that you need to run a VACUUM in any database table.
effective_io_concurrency: set the number of concurrent disk I/O operations that can run simultaneously.
hash_mem_multiplier: compute the maximum amount of memory that hash-based operations can use.
logical_decoding_work_mem: specify the maximum amount of memory that logical decoding can use before some of the decoded changes are written to a local disk.
maintenance_io_concurrency: set the number of concurrent disk I/O operations that can run simultaneously for maintenance work that's done for client sessions.
vacuum_failsafe_age: specify the maximum age (in transactions) that a database table's pg_class.relfrozenxid field can attain before a VACUUM takes extraordinary measures to avoid a system-wide wraparound failure for transaction IDs.
vacuum_multixact_failsafe_age: specify the maximum age (in multiple transactions) that a database table's pg_class.relminmxid field can attain before a VACUUM takes extraordinary measures to avoid a system-wide wraparound failure for multiple transaction IDs.

December 11, 2023

Cloud SQL for PostgreSQL

The pgvector extension, version 0.5.1 is generally available. Use this extension to store and search for vector embeddings in PostgreSQL databases. For more information, see Configure PostgreSQL extensions.

December 08, 2023

Cloud SQL for MySQL

You can now configure Cloud SQL for MySQL instances for IAM group authentication. IAM group authentication requires MySQL 8.0 and R20230909.02_00 or later. This feature is in Preview.

Cloud SQL for PostgreSQL

December 06, 2023

Cloud SQL for MySQL

The rollout of the following MySQL versions is currently underway:

MySQL 5.7.43 is upgraded to MySQL 5.7.44. For more information, see MySQL 5.7 Release Notes.

If you use a maintenance window, then the updates to the minor versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks. The new maintenance version is [MySQL version].R20231105.01_00. The details of the security fixes applied as part of this release are published in the MySQL maintenance changelog.

To learn how to check your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

November 17, 2023

Cloud SQL for MySQL

Cloud SQL now supports migrating data to an instance that already exists. You can create the instance by using Terraform or other Infrastructure-As-Code (IaC) Tools. After creating the instance, use the demote API to migrate data to it. This API demotes an existing standalone instance to be a Cloud SQL read replica for an external database server.

Cloud SQL for MySQL now supports minor version 8.0.35. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Cloud SQL for PostgreSQL

November 15, 2023

Cloud SQL for SQL Server

Cloud SQL supports the bulk insert functionality of SQL Server for importing data. This functionality is supported only on SQL Server 2022.

For more information, see Use bulk insert for importing data.

November 10, 2023

Cloud SQL for MySQL

You can now upgrade Enterprise edition instances to Enterprise Plus edition in place with minimal disruption. Similarly, you can also switch from Enterprise Plus edition to Enterprise edition in place. For more information, see Upgrade an instance by using in-place upgrade.

Cloud SQL for PostgreSQL

November 09, 2023

Cloud SQL for PostgreSQL

Data cache is now available for Cloud SQL for PostgreSQL Enterprise Plus edition instances.

November 06, 2023

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition now supports asia-southeast2 (Jakarta).

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports asia-southeast2 (Jakarta).

October 30, 2023

Cloud SQL for PostgreSQL

The rollout of the following items is complete:

The oracle_fdw extension, version 1.2
The minor versions, extension versions, and plugin versions listed in the September 21 release note

October 27, 2023

Cloud SQL for PostgreSQL

You can now specify the SSL mode of your Cloud SQL instances, which gives you more accurate SSL encryption. To use SSL mode, you must use the maintenance version [PostgreSQL version].R20230530.01_00 or newer. For more information, see Enforce SSL/TLS encryption.

October 17, 2023

Cloud SQL for MySQL

Cloud SQL supports InnoDB page compression for MySQL 5.7 and MySQL 8.0 and later.

Cloud SQL for MySQL has completed the upgrade to MySQL 5.7.43.

Cloud SQL for SQL Server

You can now import transaction log backups. This can help you reduce downtime when migrating to Cloud SQL using backups.

October 09, 2023

Cloud SQL for SQL Server

The cross db ownership chaining flag is deprecated for all SQL Server versions.

For cross-database access, use the Microsoft tutorial for signing stored procedures with a certificate.

October 02, 2023

Cloud SQL for MySQL

For Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition, you can restore backups across instances of different editions.

Cloud SQL for PostgreSQL

For Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition, you can restore backups across instances of different editions.

September 28, 2023

Cloud SQL for PostgreSQL

The following pg_wait_sampling and rdkit flags are generally available:

pg_wait_sampling flags

cloudsql.enable_pg_wait_sampling: enable the pg_wait_sampling extension for Cloud SQL for PostgreSQL instances.
pg_wait_sampling.history_size: set the size of the in-memory ring buffer for history sampling, in terms of the number of samples.
pg_wait_sampling.history_period: set the time interval for history sampling, in milliseconds.
pg_wait_sampling.profile_period: set the time interval for profile sampling for wait events, in milliseconds.
pg_wait_sampling.profile_pid: specify whether the wait profile that accumulates samples for each process and waits event is collected for each process or for all processes.
pg_wait_sampling.profile_queries: specify whether the wait profile is collected for each query or for all queries.

rdkit flags

rdkit.tanimoto_threshold: set the threshold value for the Tanimoto similarity operator.
rdkit.dice_threshold: set the threshold value for the Dice similarity operator.
rdkit.do_chiral_sss: specify whether stereochemistry is used in substructure matching.
rdkit.do_enhanced_stereo_sss: specify whether enhanced stereo is used in substructure matching.
rdkit.sss_fp_size: set the size of the fingerprint used for substructure screening, in bits.
rdkit.morgan_fp_size: set the size of morgan fingerprints, in bits.
rdkit.featmorgan_fp_size: set the size of featmorgan fingerprints, in bits.
rdkit.layered_fp_size: set the size of layered fingerprints, in bits.
rdkit.rdkit_fp_size: set the size of rdkit fingerprints, in bits.
rdkit.hashed_torsion_fp_size: set the size of topological torsion bit vector fingerprints, in bits.
rdkit.hashed_atompair_fp_size: set the size of atom pair bit vector fingerprints, in bits.
rdkit.reaction_sss_fp_size: set the size of the structural chemical reaction fingerprint, in bits.
rdkit.reaction_difference_fp_size: set the size of the difference chemical reaction fingerprint, in bits.
rdkit.reaction_sss_fp_type: specify the type of structural chemical reaction fingerprint.
rdkit.reaction_difference_fp_type: specify the type of difference chemical reaction fingerprint.
rdkit.ignore_reaction_agents: specify whether agents of a chemical reaction are taken into account.
rdkit.agent_FP_bit_ratio: specify the weight of the impact of agents contained in a chemical reaction fingerprint.
rdkit.move_unmmapped_reactants_to_agents: specify whether unmapped reactant agents of a chemical reaction are taken into account.
rdkit.threshold_unmapped_reactant_atoms: set the ratio of allowed unmapped reactant atoms.
rdkit.init_reaction: specify whether the reaction is ready for use.
rdkit.difference_FP_weight_agents: specify the weight factor for agents compared to reactants and products in reaction difference fingerprints.
rdkit.difference_FP_weight_nonagents: specify the weight factor for reactants and products compared to agents in reaction difference fingerprints.
rdkit.avalon_fp_size: set the size of avalon fingerprints, in bits.

September 26, 2023

Cloud SQL for MySQL

Cloud SQL supports the preview version of the enable-high-availability recommender. This service proactively generates recommendations that help you bring your important instances within SLA by providing data redundancy. This might be helpful during a zonal outage or when an instance runs out of memory. For more information, see Improve instance reliability by enabling high availability.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

September 25, 2023

Cloud SQL for MySQL

All Cloud SQL for MySQL Enterprise Plus edition instances now support up to 35 days of retained transaction logs for point-in-time recovery.

The rollout of the following minor version is currently underway:

MySQL 5.7.42 is upgraded to MySQL 5.7.43. For more information, see MySQL 5.7 Release Notes.

If you use a maintenance window, then the updates to the minor versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks. The new maintenance version is [MySQL version].R20230909.02_00. The details of the security fixes applied as part of this release will be published in the MySQL maintenance changelog.

To learn how to check your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

September 21, 2023

Cloud SQL for PostgreSQL

The rollout of the oracle_fdw extension, version 1.2 is underway. This extension provides a foreign data wrapper for accessing Oracle databases easily and efficiently. For more information, see Configure PostgreSQL extensions.

The rollout of the following minor versions, extension versions, and plugin versions is underway:

Minor versions

11.19 is upgraded to 11.21.
12.14 is upgraded to 12.16.
13.10 is upgraded to 13.12.
14.7 is upgraded to 14.9.
15.2 is upgraded to 15.4.

Extension and plugin versions

orafce is upgraded from 3.24.4 to 3.25.1.
pglogical is upgraded from 2.4.2 to 2.4.3.
pgvector is upgraded from 0.4.2 to 0.5.0.
PostGIS is upgraded from 3.2.3 to 3.2.5.

The new maintenance version is [PostgreSQL version].R20230830.01_00. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

September 19, 2023

Cloud SQL for MySQL

Support for me-central2 (Dammam) region.

Cloud SQL for PostgreSQL

Support for me-central2 (Dammam) region.

Cloud SQL for SQL Server

Support for me-central2 (Dammam) region.

August 31, 2023

Cloud SQL for PostgreSQL

The pgvector extension, version 0.4.2 is generally available. Use this extension to store and search for vector embeddings in PostgreSQL databases.

August 28, 2023

Cloud SQL for PostgreSQL

You can now set password policies for local database users of Cloud SQL for PostgreSQL instances.

August 22, 2023

Cloud SQL for MySQL

Support for europe-west10 (Berlin) region.

Cloud SQL for PostgreSQL

Support for europe-west10 (Berlin) region.

Cloud SQL for SQL Server

Support for europe-west10 (Berlin) region.

August 21, 2023

Cloud SQL for MySQL

Private Service Connect is now GA for Cloud SQL for MySQL. This solution allows you to connect to a Cloud SQL instance from multiple VPC networks that belong to different groups, teams, projects, or organizations.

Cloud SQL for PostgreSQL

Private Service Connect is now GA for Cloud SQL for PostgreSQL. This solution allows you to connect to a Cloud SQL instance from multiple VPC networks that belong to different groups, teams, projects, or organizations.

August 18, 2023

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition now supports four new regions:

europe-central2 (Warsaw)
europe-west9 (Paris)
southamerica-east1 (San Paulo)
us-west1 (Oregon)

Cloud SQL for MySQL now supports minor version 8.0.34. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports four new regions:

europe-central2 (Warsaw)
europe-west9 (Paris)
southamerica-east1 (San Paulo)
us-west1 (Oregon)

August 17, 2023

Cloud SQL for MySQL

You can now re-encrypt an existing Cloud SQL CMEK-enabled primary instance or replica with a new primary key version.

You can now retain up to 35 days of retention logs for your Cloud SQL for MySQL Enterprise Plus edition instances when using point-in-time recovery.

Cloud SQL for MySQL now supports storage of point-in-time recovery logs in Cloud storage.

Cloud SQL for PostgreSQL

You can now re-encrypt an existing Cloud SQL CMEK-enabled primary instance or replica with a new primary key version.

July 07, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL now supports up to 500,000 tables for instances that meet the minimum hardware requirements of 32+ cores and 200G+ memory. For more information, see table limit.

July 06, 2023

Cloud SQL for MySQL

Cloud SQL now supports non-RFC 1918 IP address ranges, including privately used public IP addresses. This enables you to create instances and replicas in a non-RFC 1918 IP address range. Additionally, you can connect to an instance from an application that is running in a non-RFC 1918 IP address range.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

June 30, 2023

Cloud SQL for MySQL

For our preferred partners and allowlisted customers, Private Service Connect is now available. This solution allows you to connect to a Cloud SQL instance from multiple VPC networks that belong to different groups, teams, projects, or organizations. To use Private Service Connect, contact your Technical Account Manager.

Cloud SQL for PostgreSQL

June 26, 2023

Cloud SQL for SQL Server

Cloud SQL now supports SQL Server 2022. The default version continues to be SQL Server 2019 Standard. For more information, see Database versions and version policies.

June 15, 2023

Cloud SQL for MySQL

The Cloud SQL System insights dashboard helps you detect and analyze system performance problems.

Cloud SQL for PostgreSQL

The Cloud SQL System insights dashboard is now generally available and includes more metrics. You can also use the Customize dashboard option to personalize the dashboard and choose the metrics you want to see on it.

June 07, 2023

Cloud SQL for SQL Server

You can now import and export differential database backups. This can help you import and export data more frequently, reducing migration downtime.

June 02, 2023

Cloud SQL for PostgreSQL

The rollout of the following minor versions, extension versions, and plugin versions is currently underway:

Minor versions

10.22 is upgraded to 10.23.
11.17 is upgraded to 11.19.
12.12 is upgraded to 12.14.
13.8 is upgraded to 13.10.
14.5 is upgraded to 14.7.

Extension and plugin versions

pg_cron is upgraded from 1.4.1 to 1.5.
pg_partman is upgraded from 4.7.0 to 4.7.3.
postgresql-hll is upgraded from 2.16 to 2.17.
pg_repack is upgraded from 1.4.7 to 1.4.8.
wal2json is upgraded from 2.4 to 2.5.
pg_hint_plan is upgraded, as follows:
- from 1.3.7 to 1.3.8 (for PostgreSQL versions 11-13)
- from 1.4.0 to 1.4.1 (for PostgreSQL version 14)
- from 1.4.0 to 1.5.0 (for PostgreSQL version 15)

The new maintenance version is [PostgreSQL version].R20230530.01_00. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

Cloud SQL for SQL Server

A vulnerability was recently discovered in Cloud SQL for SQL Server that allowed customer administrator accounts to create triggers in the tempdb database and use those to gain sysadmin privileges in the instance. The sysadmin privileges would give the attacker access to system databases and partial access to the machine running that SQL Server instance.

Google Cloud resolved the issue by patching the security vulnerability by March 1, 2023. Google Cloud didn't find any compromised customer instances.

For instructions and more details, see the Cloud SQL security bulletin.

May 24, 2023

Cloud SQL for PostgreSQL

PostgreSQL version 15 is now generally available. To start using PostgreSQL 15, see Create instances.

May 22, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.33. To upgrade your existing instance to the new version, see Upgrade the database minor version.

May 19, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL has launched two database flags that impact the Cloud SQL SLA: innodb_flush_log_at_trx_commit and sync_binlog. For more information about these flags, see supported flags.

Cloud SQL for PostgreSQL

The following extensions, views, utilities, and flags are generally available:

Extensions

postgresql_anonymizer: mask or replace personally identifiable information (PII) or sensitive data from a PostgreSQL database.
pgtt: create, manage and use Oracle-style global temporary tables.
rdkit: compare, manipulate, and identify molecular structures.

Views and utilities

pg_authid: access this catalog table that contains hashed passwords and other properties for all database roles.
pg_dumpall: extract all PostgreSQL databases of a cluster into a single script file.

Flags

log_line_prefix: generate a printf-style string at the beginning of each line of a PostgreSQL log file.

The rollout of the following minor versions, extension versions, and plugin versions is currently underway:

Minor versions

10.21 is upgraded to 10.22.
11.16 is upgraded to 11.17.
12.11 is upgraded to 12.12.
13.7 is upgraded to 13.8.
14.4 is upgraded to 14.5.

Extension and plugin versions

plv8 is upgraded from 3.1.2 to 3.1.4.
wal2json is upgraded from 2.3 to 2.4.
pgTAP is upgraded from 1.1.0 to 1.2.0.
PostGIS is upgraded from 3.1.4 to 3.1.7.
pg_partman is upgraded from 4.5.1 to 4.7.0.
pg_wait_sampling is upgraded from 1.1.3 to 1.1.4.
pg_hint_plan is upgraded from 1.3.7 to 1.4.
pglogical is upgraded from 2.4.1 to 2.4.2.

This rollout also introduces the following:

PostGIS GDAL driver support
LZ4 TOAST compression for PostgreSQL versions 14 and later

May 16, 2023

Cloud SQL for MySQL

The Cloud SQL Proxy Operator is now generally available. To learn more about the Cloud SQL Proxy Operator, see About the Cloud SQL Proxy Operator.

Cloud SQL for PostgreSQL

The Cloud SQL Proxy Operator is now generally available. To learn more about the Cloud SQL Proxy Operator, see About the Cloud SQL Proxy Operator.

Cloud SQL for SQL Server

The Cloud SQL Proxy Operator is now generally available. To learn more about the Cloud SQL Proxy Operator, see About the Cloud SQL Proxy Operator.

May 15, 2023

Cloud SQL for SQL Server

You can now use the point-in-time-recovery (PITR) feature and read replicas on the same primary instance. For more information, see Point-in-time Recovery.

May 02, 2023

Cloud SQL for PostgreSQL

Fast migration for Cloud SQL is now available. This feature improves the performance of data migrations from an external source to a destination Cloud SQL instance.

Cloud SQL for SQL Server

You can now disable simultaneous multithreading (SMT) while creating or editing instances and read replicas. This might reduce your SQL Server licensing fees. To understand the impact of disabling SMT on your instance's performance, we recommend that you perform load testing on your instance.

April 19, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL now supports 40+ new database flags. See supported flags for more information.

April 15, 2023

Cloud SQL for PostgreSQL

The changes listed in the March 29th release notes entry for PostgreSQL minor versions, extension versions, and plugin versions have been postponed.

April 06, 2023

Cloud SQL for MySQL

Cascading Replicas is now generally available when migrating from external servers. You can now configure migrated replicas to have read replicas under them before promoting them to primary replica. To learn more, see External Server Cascading Replicas.

Cloud SQL for PostgreSQL

March 30, 2023

Cloud SQL for MySQL

Support for me-central1 (Doha) region.

Cloud SQL for PostgreSQL

Support for me-central1 (Doha) region.

Cloud SQL for SQL Server

Support for me-central1 (Doha) region.

Cloud SQL supports the SqlPackage utility of SQL Server for importing and exporting data.

Cloud SQL supports the bcp utility of SQL Server for importing and exporting data.

March 29, 2023

Cloud SQL for PostgreSQL

The rollout of the following PostgreSQL minor versions, extension versions, and plugin versions is currently underway:

Minor versions

10.21 is upgraded to 10.22.
11.16 is upgraded to 11.17.
12.11 is upgraded to 12.12.
13.7 is upgraded to 13.8.
14.4 is upgraded to 14.5.

Extension and plugin versions

plv8 is upgraded from 3.1.2 to 3.1.4.
wal2json is upgraded from 2.3 to 2.4.
pgTAP is upgraded from 1.1.0 to 1.2.0.
PostGIS is upgraded from 3.1.4 to 3.1.7.
pg_partman is upgraded from 4.5.1 to 4.7.0.
pg_wait_sampling is upgraded from 1.1.3 to 1.1.4.
pg_hint_plan is upgraded from 1.3.7 to 1.4.
pglogical is upgraded from 2.4.1 to 2.4.2.

The new maintenance version is [PostgreSQL version].R20230316.02_02. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

March 28, 2023

Cloud SQL for MySQL

The changes in the September 15, 2022 Release Notes entry for read replica maintenance are now available. Cloud SQL read replicas follow the maintenance settings for the primary instance, including the maintenance window, rescheduling, and the deny maintenance period. During the maintenance event, Cloud SQL maintains the replicas before maintaining the primary instance. For more information, see How does maintenance affect read replicas?

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

Cloud SQL now exposes 38 new metrics. These metrics improve observability of Cloud SQL for SQL Server instances, helping you investigate performance issues and resource bottlenecks. You can find these metrics in the Metrics explorer within the Monitoring dashboard.

For more information about these metrics, see Cloud SQL Metrics.

March 27, 2023

Cloud SQL for SQL Server

Cloud SQL now supports the Linked Servers functionality of SQL Server. You can use this capability to integrate data from multiple sources and distribute queries across multiple servers. To learn more, see About linked servers.

The Cloud SQL Active Directory (AD) Diagnosis tool helps you troubleshoot issues that you might face while connecting to AD-enabled Cloud SQL for SQL Server instances, using an on-premises AD domain.

March 23, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.32. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Support for europe-west12 (Turin) region.

Cloud SQL for PostgreSQL

Support for europe-west12 (Turin) region.

Cloud SQL for SQL Server

Support for europe-west12 (Turin) region.

March 21, 2023

Cloud SQL for MySQL

The changes listed in the June 10 Release Notes entry for faster machine type changes were incorrect for Cloud SQL for MySQL, and only applied to Cloud SQL for PostgreSQL and Cloud SQL for SQL Server.

Cloud SQL for PostgreSQL

Smaller read replicas are now available for Cloud SQL. Read replicas no longer require the same or more CPUs and RAM than their primary instances.

March 14, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL now supports 106 new database flags. See supported flags for more information.

February 28, 2023

Cloud SQL for MySQL

Cloud SQL now supports the ability to get details for a Cloud SQL user for a database instance using the API or gcloud. To learn more about the new method, see Cloud SQL Admin API REST Resource.

Cloud SQL for PostgreSQL

Cloud SQL now supports the ability to get details for a Cloud SQL user for a database instance using the API or gcloud. To learn more about the new method, see Cloud SQL Admin API REST Resource.

Cloud SQL for SQL Server

Cloud SQL now supports the ability to get details for a Cloud SQL user for a database instance using the API or gcloud. To learn more about the new method, see Cloud SQL Admin API REST Resource.

February 24, 2023

Cloud SQL for MySQL

The Cloud SQL Proxy Operator is now available in public preview. The Cloud SQL Proxy Operator is an open-source Kubernetes operator that automates connecting workloads in a GKE cluster to Cloud SQL databases. To learn more about the Cloud SQL Proxy Operator, see About the Cloud SQL Proxy Operator.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

February 08, 2023

Cloud SQL for MySQL

The Cloud SQL Auth proxy is a utility for ensuring secure connections to your Cloud SQL instances. The v2 release offers improvements in performance, stability, and telemetry. Among the new features, there's support for:

Metrics and tracing with Cloud Monitoring and Cloud Trace
Support for Prometheus
Service account impersonation
Separate Dialer functionality released as the Cloud SQL Go Connector
Configuration with environment variables
Fully POSIX-compliant flags

We recommend all customers upgrade to v2 and have released a migration guide. For more information, see Cloud SQL Auth proxy.

Cloud SQL for PostgreSQL

Metrics and tracing with Cloud Monitoring and Cloud Trace
Support for Prometheus
Service account impersonation
Separate Dialer functionality released as the Cloud SQL Go Connector
Configuration with environment variables
Fully POSIX-compliant flags

We recommend all customers upgrade to v2 and have released a migration guide. For more information, see Cloud SQL Auth proxy.

Cloud SQL for SQL Server

Metrics and tracing with Cloud Monitoring and Cloud Trace
Support for Prometheus
Service account impersonation
Separate Dialer functionality released as the Cloud SQL Go Connector
Configuration with environment variables
Fully POSIX-compliant flags

We recommend all customers upgrade to v2 and have released a migration guide. For more information, see Cloud SQL Auth proxy.

February 02, 2023

Cloud SQL for MySQL

Cloud SQL supports the preview version of the Underprovisioned instance recommender. This service helps you avoid bottlenecks from high CPU and memory usage and minimize the likelihood of out-of-memory events. It gives you recommendations to resize your instances to a machine tier that better suits your workload.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

January 19, 2023

Cloud SQL for MySQL

MySQL 8.0.29 was deprecated on January 19, 2023. You will not be able to create new instances for MySQL 8.0.29, upgrade existing instances to MySQL 8.0.29, or promote an existing MySQL 8.0.29 replica to primary. For more information, see Changes in MySQL 8.0.29.

If you have a MySQL 8.0.29 instance, it will automatically be upgraded to MySQL 8.0.30 as part of regular maintenance prior to March 31, 2023. You can also upgrade your instance to higher available versions. See Upgrade the database minor version for more information.

January 18, 2023

Cloud SQL for MySQL

Cloud SQL now supports viewing an audit log for an automated backup of an instance to verify whether the backup is completed successfully. You can also configure a log-based alert so that a user can be notified of the backup's status.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

Cloud SQL for SQL Server enables you to use point-in-time recovery.

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. This feature is generally available.

January 17, 2023

Cloud SQL for MySQL

Cloud SQL for MySQL now supports using the lower_case_table_names flag for MySQL 8.0. For more information, see Configure database flags.

January 10, 2023

Cloud SQL for SQL Server

You can use striped import and striped export to reduce the time needed for BAK file operations and for other purposes. This feature is generally available.

January 09, 2023

Cloud SQL for PostgreSQL

For new Cloud SQL instances that have point-in-time recovery enabled or for existing instances that enable point-in-time recovery, Cloud SQL for PostgreSQL now stores write-ahead logs in Google Cloud Storage.

Before this release, write-ahead logs, which are used to perform point-in-time recovery, were stored on disk. Now, logs are stored in Google Cloud Storage in the same region as the instances.

All other existing instances that have point-in-time recovery enabled will continue to have their logs stored on disk. The change to storing logs in Google Cloud Storage will be made available at a later time.

December 27, 2022

Cloud SQL for MySQL

The changes listed in the December 20 release notes entry for the lower_case_table_names flag for MySQL 8.0 have been postponed.

December 21, 2022

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.31. To upgrade your existing instance to the new version, see Upgrade the database minor version.

December 20, 2022

Cloud SQL for MySQL

Cloud SQL for MySQL now supports using the lower_case_table_names flag for MySQL 8.0. For more information, see Configure database flags.

December 16, 2022

Cloud SQL for MySQL

Automatic IAM database authentication for Cloud SQL for MySQL is now available. To get started using automatic IAM database authentication, see Cloud SQL IAM database authentication.

MySQL 5.7.38 has been upgraded to 5.7.39. For more information, see MySQL 5.7 release notes.

December 15, 2022

Cloud SQL for MySQL

You can now allow other Google Cloud services, such as BigQuery, to access data in Cloud SQL for MySQL and make queries against this data over a private connection. For more information, see Create instances.

Cloud SQL for PostgreSQL

You can now allow other Google Cloud services, such as BigQuery, to access data in Cloud SQL for PostgreSQL and make queries against this data over a private connection. For more information, see Create instances.

December 13, 2022

Cloud SQL for PostgreSQL

The Cloud SQL System insights dashboard now shows additional metrics and an events timeline. You can also use the Auto refresh function to keep the dashboard up to date.

December 01, 2022

Cloud SQL for PostgreSQL

The changes listed in the October 19th release notes entry for PostgreSQL minor versions, extension versions, and plugin versions have been postponed.

October 28, 2022

Cloud SQL for MySQL

The changes listed in the September 15 Release Notes entry for read replica maintenance have been postponed.

Cloud SQL for PostgreSQL

The changes listed in the September 15 Release Notes entry for read replica maintenance have been postponed.

Cloud SQL for SQL Server

The changes listed in the September 15 Release Notes entry for read replica maintenance have been postponed.

October 19, 2022

Cloud SQL for PostgreSQL

The rollout of the following PostgreSQL minor versions, extension versions, and plugin versions is currently underway:

Minor versions

10.21 is upgraded to 10.22.
11.16 is upgraded to 11.17.
12.11 is upgraded to 12.12.
13.7 is upgraded to 13.8.
14.4 is upgraded to 14.5.

Extension and plugin versions

plv8 is upgraded from 3.1.2 to 3.1.4.
wal2json is upgraded from 2.3 to 2.4.
pgTAP is upgraded from 1.1.0 to 1.2.0.
PostGIS is upgraded from 3.1.4 to 3.1.7.

In addition, this rollout introduces the following changes to collation support:

The C.UTF-8 collation is renamed to C.utf8. The original name is supported as an alias of the new name.
The following collations aren't supported anymore:
- as_IN.utf8
- az_AZ.utf8
- ca_ES.utf8@valencia
- eo.utf8
- ia
- iw_IL
- iw_IL.utf8
- pap_AN
- tt_RU.utf8
- tt_RU.utf8@iqtelif

The new maintenance version is [PostgreSQL version].R20221017.01_00. To learn how to check your maintenance version, see Self service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

October 11, 2022

Cloud SQL for MySQL

Cloud SQL supports the preview version of the following recommenders that help you optimize your instance's performance:

High number of open tables recommender: Optimize the performance of your instance by increasing the size of table open cache for the Cloud SQL instances that have the number of open tables equal to the table open cache and keep opening too many tables concurrently
High number of tables recommender: Optimize the performance of your instance by reducing the number of tables for the Cloud SQL instances whose table count is too high and close to the SLA limit.

Cloud SQL for PostgreSQL

Cloud SQL supports the preview version of the high transaction ID utilization recommender that helps you avoid potential transaction ID wraparound for Cloud SQL for PostgreSQL instances.

October 07, 2022

Cloud SQL for SQL Server

When you create an instance, you can set a permanent time zone for the instance. This feature is generally available.

October 05, 2022

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL now supports the log_timezone and TimeZone flags. For more information, see the Configure database flags page.

October 04, 2022

Cloud SQL for MySQL

Terraform is supported when you use self-service maintenance.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

September 13, 2022

Cloud SQL for MySQL

Support for me-west1 (Tel Aviv).

MySQL 5.7.37 has been upgraded to 5.7.38. For more information, see MySQL 5.7 release notes.

Cloud SQL for PostgreSQL

Support for me-west1 (Tel Aviv).

Cloud SQL for SQL Server

Support for me-west1 (Tel Aviv).

September 12, 2022

Cloud SQL for MySQL

The In-place Major Version Upgrade feature is now generally available for Cloud SQL for MySQL.

Cascading Replicas is now generally available for Cloud SQL. Customers can now configure PostgreSQL and MySQL for Cloud SQL read replicas to have read replicas under them.

Cloud SQL for PostgreSQL

Cascading Replicas is now generally available for Cloud SQL. Customers can now configure PostgreSQL and MySQL for Cloud SQL read replicas to have read replicas under them.

September 06, 2022

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.30. To upgrade your existing instance to the new version, see Upgrade the database minor version.

August 26, 2022

Cloud SQL for PostgreSQL

The following extensions in Cloud SQL for PostgreSQL are generally available:

pgRouting. Enhances geospatial processing, through network routing and analysis, for PostGIS.
plv8. Provides a procedural language for enabling the use of JavaScript.
amcheck. Enables the use of the pg_amcheck application to check for corruption in PostgreSQL databases.

August 22, 2022

Cloud SQL for SQL Server

Cloud SQL may set a value for the max server memory (mb) flag on instances, based on Microsoft's recommended values. For information about flags supported by Cloud SQL, see Configure database flags.

August 15, 2022

Cloud SQL for MySQL

By enabling instance deletion protection, you can prevent the accidental removal of Cloud SQL instances. This functionality is generally available.

For more information, see Prevent deletion of an instance.

Cloud SQL for PostgreSQL

By enabling instance deletion protection, you can prevent the accidental removal of Cloud SQL instances. This functionality is generally available.

For more information, see Prevent deletion of an instance.

Cloud SQL for SQL Server

By enabling instance deletion protection, you can prevent the accidental removal of Cloud SQL instances. This functionality is generally available.

For more information, see Prevent deletion of an instance.

August 05, 2022

Cloud SQL for PostgreSQL

The new Cloud SQL System insights dashboard helps you detect and analyze system performance problems.

July 29, 2022

Cloud SQL for PostgreSQL

For PostgreSQL versions 9.6 to 13, the [PostgreSQL version].R20220710.01_00 maintenance version caused a behavior change for configuration parameters: Session-level configuration parameters with dashes (-) cannot be set.

After you check your current maintenance version, you can apply a fix by performing a self-service maintenance update to the latest release.

Please use this table to find the name of the maintenance version to apply, and use that version or the latest version available:

PostgreSQL version	Maintenance version
PostgreSQL 9.6	POSTGRES_9_6_24.R20220710.01_02
PostgreSQL 10	POSTGRES_10_21.R20220710.01_02
PostgreSQL 11	POSTGRES_11_16.R20220710.01_02
PostgreSQL 12	POSTGRES_12_11.R20220710.01_02
PostgreSQL 13	POSTGRES_13_7.R20220710.01_02

After you have identified the name of the maintenance version, please upgrade to the target maintenance version, performing the corresponding update of your instances (to the latest maintenance version).

Note that newly created instances automatically use the latest version.

July 25, 2022

Cloud SQL for PostgreSQL

The following PostgreSQL minor versions and extension versions are now available:

14.3 is upgraded to 14.4.
13.6 is upgraded to 13.7.
12.10 is upgraded to 12.11.
11.15 is upgraded to 11.16.
10.20 is upgraded to 10.21.

If you use maintenance windows, then you might not yet have these versions. In this case, you'll see the new versions after your maintenance update occurs. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

Added information about checking the LC_COLLATE value for your databases before performing a major version upgrade of the databases for your Cloud SQL for PostgreSQL instance. For more information, refer to the Cloud SQL documentation.

July 14, 2022

Cloud SQL for MySQL

For enhanced security with built-in authentication, Cloud SQL now lets you set password policies at the instance and user levels.

July 11, 2022

Cloud SQL for MySQL

You can enable high availability for read replicas. See Disaster recovery for additional information about the use of high-availability replicas in a disaster recovery configuration.

You can create external server replicas with HA enabled.

Cloud SQL for PostgreSQL

You can enable high availability for read replicas. See Disaster recovery for additional information about the use of high-availability replicas in a disaster recovery configuration.

You can create external server replicas with HA enabled.

Cloud SQL for SQL Server

The database major version upgrade feature of Cloud SQL for SQL Server is generally available. For more information, see Upgrade the database major version in-place.

July 08, 2022

Cloud SQL enables you to access to the pg_shadow view. You can use the pg_shadow view to work with the properties of roles that are marked as rolcanlogin in the pg_authid catalog.

For more information, see Access to the pg_shadow view.

June 10, 2022

Cloud SQL for MySQL

Cloud SQL now supports faster machine type changes, with connectivity dropping to less than 60 seconds. For more information, see Impact of changing instance settings.

MySQL 5.7.36 has been upgraded to 5.7.37.

Cloud SQL for PostgreSQL

Cloud SQL now supports faster machine type changes, with connectivity dropping to less than 60 seconds. For more information, see Impact of changing instance settings.

Cloud SQL for SQL Server

Cloud SQL now supports faster machine type changes, with connectivity dropping to less than 60 seconds. For more information, see Impact of changing instance settings.

June 09, 2022

Cloud SQL for MySQL

The June maintenance changelog is now available. For more information, use the links at Maintenance changelog.

Cloud SQL for PostgreSQL

The June maintenance changelog is now available. For more information, use the links at Maintenance changelog.

Cloud SQL for SQL Server

The June maintenance changelog is now available. For more information, use the links at Maintenance changelog.

June 08, 2022

Cloud SQL for MySQL

An addendum to the May maintenance changelog shows additional security patches. For more information, use the links at Maintenance changelog.

Cloud SQL for PostgreSQL

New maintenance versions are now available through self-service maintenance. See the maintenance changelog to learn more about these new maintenance versions.

An addendum to the May maintenance changelog shows additional security patches. For more information, use the links at Maintenance changelog.

Cloud SQL for SQL Server

An addendum to the May maintenance changelog shows additional security patches. For more information, use the links at Maintenance changelog.

June 07, 2022

Cloud SQL for MySQL

Support for us-south1 (Dallas).

Cloud SQL for PostgreSQL

Support for us-south1 (Dallas).

Cloud SQL for SQL Server

Support for us-south1 (Dallas).

May 26, 2022

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor version 8.0.29. To upgrade your existing instance to the new version, see Upgrade the database minor version.

May 24, 2022

Cloud SQL for MySQL

Support for us-east5 (Columbus).

Cloud SQL for PostgreSQL

Support for us-east5 (Columbus).

Cloud SQL for SQL Server

Cloud SQL for MySQL

MySQL 8.0 is now the default major database version for Cloud SQL for MySQL.

April 28, 2022

Cloud SQL for MySQL

The following Cloud SQL recommenders that help you optimize your database costs are now generally available:

Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.
Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

Cloud SQL for PostgreSQL

The following Cloud SQL recommenders that help you optimize your database costs are now generally available:

Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.
Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

Cloud SQL for SQL Server

The following Cloud SQL recommenders that help you optimize your database costs are now generally available:

Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.
Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

April 25, 2022

Cloud SQL for MySQL

You can now accept a maintenance update on your instance outside of the normal flow of scheduled maintenance.

While Cloud SQL schedules maintenance updates once every few months to ensure you have the latest maintenance version, you might want to use self-service maintenance if:

You need an update sooner than your next scheduled maintenance event.
You want to catch up to the latest maintenance version after skipping your most recent scheduled maintenance event.
You want to gain more control over when maintenance is applied

Cloud SQL now supports maintenance changelogs. Maintenance changelogs provide information about updates available in new maintenance versions, such as database minor version upgrades and patches for security vulnerabilities. For links to current maintenance changelogs for each major database version, see Cloud SQL maintenance changelogs.

Cloud SQL for PostgreSQL

You can now accept a maintenance update on your instance outside of the normal flow of scheduled maintenance.

While Cloud SQL schedules maintenance updates once every few months to ensure you have the latest maintenance version, you might want to use self-service maintenance if:

You need an update sooner than your next scheduled maintenance event.
You want to catch up to the latest maintenance version after skipping your most recent scheduled maintenance event.
You want to gain more control over when maintenance is applied

The following PostgreSQL minor versions and extension versions are now available. If you use maintenance windows, you might not yet have these versions. In this case, you will see the new versions after your maintenance update occurs. To find your maintenance window or manage maintenance updates, see Finding and setting maintenance windows.

14.1 is upgraded to 14.2.
13.5 is upgraded to 13.6.
12.9 is upgraded to 12.10.
11.14 is upgraded to 11.15.
10.19 is upgraded to 10.20.

Cloud SQL for SQL Server

You can now accept a maintenance update on your instance outside of the normal flow of scheduled maintenance.

While Cloud SQL schedules maintenance updates once every few months to ensure you have the latest maintenance version, you might want to use self-service maintenance if:

You need an update sooner than your next scheduled maintenance event.
You want to catch up to the latest maintenance version after skipping your most recent scheduled maintenance event.
You want to gain more control over when maintenance is applied

April 20, 2022

Cloud SQL for MySQL

Support for europe-west8 region (Milan).

Cloud SQL for PostgreSQL

Support for europe-west8 region (Milan).

Cloud SQL for SQL Server

Support for europe-west8 region (Milan).

April 12, 2022

Cloud SQL for MySQL

Customer-managed encryption key (CMEK) organization policy constraints are now available in Preview.

constraints/gcp.restrictNonCmekServices allows you to control which resources require the use of CMEK.
constraints/gcp.restrictCmekCryptoKeyProjects allows you to control the projects from which a Cloud KMS key can be used to validate requests.

You can use both constraints together to enforce the use of CMEK from allowed projects.

To learn more, see Customer-managed encryption keys (CMEK) organization policies. To add CMEK organization policies now, see Add Cloud SQL organization policies.

Cloud SQL for PostgreSQL

Customer-managed encryption key (CMEK) organization policy constraints are now available in Preview.

constraints/gcp.restrictNonCmekServices allows you to control which resources require the use of CMEK.
constraints/gcp.restrictCmekCryptoKeyProjects allows you to control the projects from which a Cloud KMS key can be used to validate requests.

You can use both constraints together to enforce the use of CMEK from allowed projects.

To learn more, see Customer-managed encryption keys (CMEK) organization policies. To add CMEK organization policies now, see Add Cloud SQL organization policies.

Cloud SQL for SQL Server

Customer-managed encryption key (CMEK) organization policy constraints are now available in Preview.

constraints/gcp.restrictNonCmekServices allows you to control which resources require the use of CMEK.
constraints/gcp.restrictCmekCryptoKeyProjects allows you to control the projects from which a Cloud KMS key can be used to validate requests.

You can use both constraints together to enforce the use of CMEK from allowed projects.

To learn more, see Customer-managed encryption keys (CMEK) organization policies. To add CMEK organization policies now, see Add Cloud SQL organization policies.

April 11, 2022

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL supports in-place major version upgrades in Preview. You can upgrade your instance's major version to a more recent version. For more information, see Upgrade the database major version in-place.

Cloud SQL for SQL Server

Cloud SQL for SQL Server supports in-place upgrades in Preview. You can upgrade your instance's major version or edition. For more information, see Upgrade the database major version in-place.

April 01, 2022

Cloud SQL for MySQL

Cloud SQL for MySQL now supports minor versions 8.0.27 and 8.0.28. To upgrade your existing instance to the new version, see Upgrade the database minor version.

February 28, 2022

Cloud SQL for MySQL

Cloud SQL for MySQL 8.0.26 is now the default minor version. To upgrade your existing instance to the new version, see Set the MySQL minor version.

February 24, 2022

Cloud SQL for PostgreSQL

Due to a change in a recent maintenance update, the changes listed in the February 4 Release Notes entry have been applied to some instances but postponed for the others. In the Google Cloud Console, you can determine if the maintenance update was applied. Specifically, on the Instance Overview page, review the instance's operations and logs for an occurrence of a maintenance operation since January 27.

February 23, 2022

Cloud SQL for MySQL

If your primary instance uses a private IP address, you can now select an allocated IP range for clones and replicas created from the instance.

Cloud SQL for PostgreSQL

If your primary instance uses a private IP address, you can now select an allocated IP range for clones and replicas created from the instance.

Cloud SQL for SQL Server

If your primary instance uses a private IP address, you can now select an allocated IP range for clones and replicas created from the instance.

February 17, 2022

Cloud SQL for MySQL

Cloud SQL now supports the use of tags on instances. Tags are key-value pairs you can apply to your resources, such as a project or a Cloud SQL instance, which are used for fine-grained access control. To learn more, see Access control with Google Cloud tags. To use tags now, see Attach and manage tags on Cloud SQL instances.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

February 08, 2022

Cloud SQL for PostgreSQL

Cloud SQL supports the max_parallel_maintenance_workers, max_parallel_workers,
max_parallel_workers_per_gather, and max_pred_locks_per_transaction flags:

max_parallel_maintenance_workers sets the maximum number of parallel workers that can be started by a single utility command.
max_parallel_workers sets the maximum number of workers that the system can support for parallel operations.
max_parallel_workers_per_gather sets the maximum number of workers that can be started by a single Gather or Gather Merge node.
max_pred_locks_per_transaction controls the average number of object locks allocated for each transaction.

For more information, see Supported flags.

Cloud SQL for SQL Server

Cross-region replication is now generally available in Cloud SQL for SQL Server.

You can use replication to scale the use of data in a database without degrading performance. Other reasons include migrating or maintaining data duplicates between regions.

For more information, see Replication in Cloud SQL.

February 07, 2022

Cloud SQL for PostgreSQL

Cloud SQL supports the wal_receiver_timeout and wal_sender_timeout flags:

The wal_receiver_timeout flag ends replication connections that are inactive for the specified time.
The wal_sender_timeout flag, which is for detection by the ending server, ends replication connections that are inactive for the specified time.

For more information, see Supported flags.

Cloud SQL for SQL Server

SQL Server 2019 is now the default version. See Database versions and version policies.

February 04, 2022

Cloud SQL for PostgreSQL

14.0 is upgraded to 14.1.
13.4 is upgraded to 13.5.
12.8 is upgraded to 12.9.
11.13 is upgraded to 11.14.
10.18 is upgraded to 10.19.
9.6.23 is upgraded to 9.6.24.

Additionally, the following extensions have been upgraded. For more information about these and other extensions, see PostgreSQL extensions.

The pglogical extension is upgraded to 2.4.1.
The pgaudit extension is upgraded as follows:
- For PostgreSQL 14, upgraded to 1.6.1.
- For PostgreSQL 13, upgraded to 1.5.1.
- For PostgreSQL 12, upgraded to 1.4.2.
- For PostgreSQL 11, upgraded to 1.3.3.
- For PostgreSQL 10, upgraded to 1.2.3.
- For PostgreSQL 9.6, upgraded to 1.1.4.

February 01, 2022

Cloud SQL for PostgreSQL

Query Insights lets you configure the query sampling rate. For information, see Using Query Insights to improve query performance.

January 31, 2022

Cloud SQL for MySQL

The Key Access Justifications (KAJ) feature is now generally available in Cloud SQL. You can use KAJ as part of Cloud External Key Manager (EKM). KAJ enables you to view the reason for each Cloud EKM request. Additionally, based on the justification provided, you can automatically approve or deny a request. For related information, see the Overview.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

December 16, 2021

Cloud SQL for MySQL

You can now see the database minor version when viewing information about an instance. See Database versions and version policies for a list of the latest supported versions.

You can now set or upgrade your minor version for Cloud SQL for MySQL 8.0.

Cloud SQL now supports MySQL 8.0.26. To upgrade your existing instance to the new version, see how to upgrade your minor version.

MySQL 5.7.35 has been upgraded to 5.7.36.

Cloud SQL for MySQL now supports point-in-time recovery using a timestamp. See Point-in-time recovery.

Cloud SQL for MySQL now supports database auditing. Database auditing lets you track specific user actions in the database, such as table updates, read queries, user privilege grants, and others. To learn more, see MySQL database auditing.

Cloud SQL for PostgreSQL

You can now see the database minor version when viewing information about an instance. See Database versions and version policies for a list of the latest supported versions.

Cloud SQL for SQL Server

You can now see the database minor version when viewing information about an instance. See Database versions and version policies for a list of the latest supported versions.

December 15, 2021

Cloud SQL for PostgreSQL

PostgreSQL version 14 is now generally available. To start using PostgreSQL 14, see Create instances.

December 13, 2021

Cloud SQL for SQL Server

A new feature enables more flexibility for integrating Cloud SQL for SQL Server with Managed Service for Microsoft Active Directory. You can integrate your SQL Server instance with a managed AD domain located in a different project.

December 09, 2021

Cloud SQL for MySQL

Cloud SQL now limits the rate for backup and restore operations on the data disk. For more information, see Backup rate limitations and Restore rate limitations.

Cloud SQL for PostgreSQL

Cloud SQL now limits the rate for backup and restore operations on the data disk. For more information, see Backup rate limitations and Restore rate limitations.

November 19, 2021

Cloud SQL for PostgreSQL

The following extensions in Cloud SQL for PostgreSQL are generally available:

auto_explain. Enables you to automatically log execution plans of slow statements, for troubleshooting and more. Provides an automated way to perform the functionality of the EXPLAIN command.
pg_cron. A cron-based job scheduler, this extension enables cron syntax to schedule commands from a database.
pg_hint_plan. Enables you to improve PostgreSQL execution plans using hints, which are simple descriptions in SQL comments.
pg_proctab. Enables you to use pg_top with Cloud SQL for PostgreSQL, and generate reports from the operating system process table.

November 16, 2021

Cloud SQL for MySQL

Support for southamerica-west1 (Santiago) region.

Cloud SQL for PostgreSQL

Support for southamerica-west1 (Santiago) region.

Cloud SQL for SQL Server

Support for southamerica-west1 (Santiago) region.

October 29, 2021

Cloud SQL for PostgreSQL

The following PostgreSQL minor versions and extension versions are now available. If you use maintenance windows, you might not yet have these versions. In this case, you will see the new versions after your maintenance update occurs. To find your maintenance window or manage maintenance updates, see Finding and setting maintenance windows.
- 9.6.22 is upgraded to 9.6.23.
- 10.17 is upgraded to 10.18.
- 11.12 is upgraded to 11.13.
- 12.7 is upgraded to 12.8.
- 13.3 is upgraded to 13.4.
The hll extension is upgraded to 2.16.
The pglogical extension is upgraded to 2.4.0.
The pg_partman extension is upgraded to 4.5.1.
The pg_repack extension is upgraded to 1.4.7.

October 26, 2021

Cloud SQL for PostgreSQL

Cloud SQL now supports the max_pred_locks_per_page and max_pred_locks_per_relation flags. For information about the Cloud SQL implementation of these flags, see Supported flags.

October 08, 2021

Cloud SQL for MySQL

Access Approval is now GA for Cloud SQL. Access Approval enables you to require explicit approval before Google Support may access your database for support purposes.To learn about access approval, see Overview of Access Approval. To set up access approval now, see the Access Approval Quickstart.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

October 04, 2021

Cloud SQL for MySQL

Cloud SQL now supports the ability for you to specify IP CIDR ranges from your VPC network for your Cloud SQL instances allowing you to manage your IP address space better. For more information, see Allocated IP address ranges. To start using this feature now, see Configuring private IP for a new instance.

September 28, 2021

Cloud SQL for MySQL

Cloud SQL supports the preview version of two recommenders that help you optimize your database costs:

Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.
Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

When a database instance is nearly out of storage capacity, it's automatically stopped to prevent the loss of information. For more information, see Stopping an instance.

Cloud SQL for PostgreSQL

Cloud SQL supports the preview version of two recommenders that help you optimize your database costs:

Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.
Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

When a database instance is nearly out of storage capacity, it's automatically stopped to prevent the loss of information. For more information, see Stopping an instance.

Cloud SQL for SQL Server

Cloud SQL supports the preview version of two recommenders that help you optimize your database costs:

Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.
Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

When a database instance is nearly out of storage capacity, it's automatically stopped to prevent the loss of information. For more information, see Stopping an instance.

September 14, 2021

Cloud SQL for MySQL

Cloud SQL for MySQL now supports custom formatting controls for CSVs. For more information on how to select custom characters for field delimiters, quotes, escapes, and other characters in admin exports and imports, see our documentation.

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL has enhanced the support for multiline log entries in postgres.log. Before, when a log entry spanned multiple lines, each line was recorded as a separate entry in Cloud Logging. The lines are now recorded as a single entry in Cloud Logging for ease of query and processing.

Cloud SQL for PostgreSQL now supports custom formatting controls for CSVs. For more information on how to select custom characters for field delimiters, quotes, escapes, and other characters in admin exports and imports, see our documentation.

September 10, 2021

Cloud SQL for MySQL

The Cloud SQL out-of-disk recommender is now generally available. This feature proactively generates recommendations that help you reduce the risk of downtime that might be caused by your instances running out of disk space.

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL now supports the min_wal_size flag. For more information about this flag, see the Cloud SQL for PostgreSQL flags documentation.

Cloud SQL for SQL Server

September 08, 2021

Cloud SQL for MySQL

Cloud SQL for MySQL now allows you to specify mysqldump options during migration from external servers. For more information, see Configuring Cloud SQL to replicate from an external server and Using a managed import to set up replication from external databases.

September 02, 2021

Cloud SQL for MySQL

Cloud SQL for MySQL now supports using a custom import to set up replication from large external databases. To use this replication option, see Configuring Cloud SQL to replicate from an external server and Using a custom import to set up replication from large external databases.

August 30, 2021

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL support for pglogical, native logical replication, and change data capture (CDC) using wal2json and test_decoding is now generally available.

Cloud SQL for PostgreSQL support for Automatic IAM database authentication is now generally available. See Automatic IAM database authentication.

August 27, 2021

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL now supports the following flags:

huge_pages
shared_buffers
wal_buffers

For more information about these flags, see the Cloud SQL for PostgreSQL flags documentation.

August 21, 2021

Cloud SQL for MySQL

Cloud SQL now supports IAM Conditions.

You can use IAM Conditions to define and enforce conditional, attribute-based access control for Google Cloud resources, including Cloud SQL instances. See Overview of IAM Conditions for more information.

Cloud SQL for PostgreSQL

Cloud SQL now supports IAM Conditions.

Cloud SQL for SQL Server

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL now supports the following flags:
- tcp_keepalives_count
- tcp_keepalives_idle
- tcp_keepalives_interval

For more information about these flags, see the Cloud SQL for PostgreSQL flags documentation.

July 26, 2021

Cloud SQL for PostgreSQL

The following PostgreSQL minor versions and extension versions are now available. If you use maintenance windows, you might not yet have these versions. In this case, you will see the new versions once your maintenance update occurs. To find your maintenance window or manage maintenance updates, see Finding and setting maintenance windows.
- 9.6.21 is upgraded to 9.6.22.
- 10.16 is upgraded to 10.17.
- 11.11 is upgraded to 11.12.
- 12.6 is upgraded to 12.7.
- 13.2 is upgraded to 13.3.
pglogical extension is upgraded to 2.3.4.
PostGIS extension is upgraded to 3.0.3 for all PostgreSQL major versions.

July 08, 2021

The following MySQL minor versions have been upgraded:

MySQL 5.6.50 is upgraded to 5.6.51
MySQL 5.7.32 is upgraded to 5.7.33

Cloud SQL for PostgreSQL

Cloud SQL storage limits are now increased to support up to 64 TB. See Cloud SQL storage limits for more information.

Cloud SQL for SQL Server

Cloud SQL storage limits are now increased to support up to 64 TB. See Cloud SQL storage limits for more information.

June 21, 2021

Cloud SQL for MySQL

Support for australia-southeast2 (Melbourne) region.

Cloud SQL for PostgreSQL

Support for australia-southeast2 (Melbourne) region.

Cloud SQL for SQL Server

A preview enables you to use replication in Cloud SQL for SQL Server. Additionally, the preview enables you to make cross-region replicas.

You can use replication to scale the use of data in a database without degrading performance. Other reasons include migrating or maintaining data duplicates between regions.

For more information, see Replication in Cloud SQL.

Support for australia-southeast2 (Melbourne) region.

June 17, 2021

Cloud SQL for PostgreSQL

Query Insights is now supported for read replicas.

June 07, 2021

Cloud SQL for MySQL

Cloud SQL now offers faster maintenance, with connectivity dropping for less than 60 seconds on average.

Cloud SQL for PostgreSQL

Cloud SQL now offers faster maintenance, with connectivity dropping for less than 60 seconds on average.

Cloud SQL for SQL Server

Cloud SQL now offers faster maintenance, with connectivity dropping for less than 120 seconds on average.

June 04, 2021

Cloud SQL for PostgreSQL

Both the Cloud SQL Java Connector and Cloud SQL Python Connector now support IAM Authentication for PostgreSQL.

June 01, 2021

Cloud SQL for MySQL

Cloud SQL for MySQL now supports the MySQL flags expire_logs_days (for MySQL 5.6 and 5.7) and binlog_expire_logs_seconds (for MySQL 8.0). Note that if you enable point-in-time recovery, the expiration period of your binary logs will be determined by the lesser of your transaction log retention period and the value of these flags.

Cloud SQL for PostgreSQL

The logical replication and decoding functionality of PostgreSQL is available as a preview. These features enable logical replication workflows and change data capture workflows.

For more information, see Setting up logical replication and decoding.

Cloud SQL for PostgreSQL now supports the pg_similarity extension, which provides support for similarity queries in PostgreSQL.

Also, the default value for the database flag autovacuum_vacuum_cost_delay is changed to 2 milliseconds in PostgreSQL 9.6, 10 and 11.

The minor versions for various extensions have also been upgraded:

	9.6	10	11	12	13
address_standardizer	not avail	2.4.9	2.5.5	3.0.2	3.0.2
hll	2.14	2.14	2.14	2.14	2.14
pg_repack	1.4.6	1.4.6	1.4.6	1.4.6	1.4.6
pgaudit	1.1.3	1.2.3	1.3.2	1.4.1	no change
pglogical	2.3.3	2.3.3	2.3.3	2.3.3	2.3.3
pl/proxy	2.10.0	2.10.0	2.10.0	2.10.0	2.10.0
postgis	2.3.11	2.4.9	2.5.5	3.0.2	3.0.2

May 19, 2021

Cloud SQL for MySQL

Cloud SQL supports the preview version of the out-of-disk recommender. This feature proactively generates recommendations that help you reduce the risk of downtime that might be caused by your instances running out of disk space. These recommendations can be applied when a Cloud SQL instance is trending towards the storage limit.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

April 30, 2021

Cloud SQL for SQL Server

The following version upgrade applies to Cloud SQL for SQL Server:

SQL Server 2017 is upgraded from 14.0.3257.3 to 14.0.3370.1

If you use maintenance windows, the new version will be available after your maintenance update. For information about maintenance windows, and to manage maintenance updates, see Finding and setting maintenance windows.

April 23, 2021

Cloud SQL for PostgreSQL

The 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.

9.6.20 is upgraded to 9.6.21.
10.15 is upgraded to 10.16.
11.10 is upgraded to 11.11.
12.5 is upgraded to 12.6.
13.1 is upgraded to 13.2.

For more information about the content of these minor versions, please see the PostgreSQL release notes.

April 06, 2021

Cloud SQL for PostgreSQL

Cloud 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

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 PostgreSQL

Cloud SQL for PostgreSQL flags are now generally available. See supported PostgreSQL flags for more information.

March 29, 2021

Cloud SQL for SQL Server

You 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 MySQL

Support for europe-central2 (Warsaw ).

Cloud SQL for PostgreSQL

Support for europe-central2 (Warsaw ).

Cloud SQL for SQL Server

Support for europe-central2 (Warsaw ).

March 19, 2021

Cloud SQL for PostgreSQL

The 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 MySQL

Cloud 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 MySQL

The 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 MySQL

Cloud SQL now offers faster maintenance, with average connectivity loss lasting 90 seconds or less on average. See more about maintenance timelines.

Cloud SQL for PostgreSQL

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 PostgreSQL

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 MySQL

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.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

January 28, 2021

Cloud SQL for PostgreSQL

Query 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 Improving query performance.

January 19, 2021

Cloud SQL for PostgreSQL

Database 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 MySQL

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 for PostgreSQL

For more information about database/memory/total_usage, see Cloud SQL Metrics.

Cloud SQL for SQL Server

For more information about database/memory/total_usage, see Cloud SQL Metrics.

December 21, 2020

Cloud SQL for PostgreSQL

IAM 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 MySQL

In Cloud SQL for MySQL, parallel replication is generally available for improving replication performance.

Cloud SQL for PostgreSQL

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 PostgreSQL

Cloud SQL for PostgreSQL now supports the effective_cache_size flag.

November 19, 2020

Cloud SQL for MySQL

Cloud 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

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

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 PostgreSQL

PostgreSQL version 13 is now generally available. To start using PostgreSQL 13, see Creating instances.

October 30, 2020

Cloud SQL for MySQL

In Cloud SQL for MySQL, 80 supported flags that previously were in beta are now generally available.

October 21, 2020

Cloud SQL for MySQL

Cloud SQL for MySQL supports binary logging on read replicas for MySQL versions 5.7 and 8.0.

October 12, 2020

Cloud SQL for MySQL

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.

Cloud SQL for PostgreSQL

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.

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 for SQL Server

September 24, 2020

Cloud SQL for MySQL

MySQL 5.6.42 is upgraded to 5.6.47.

September 21, 2020

Cloud SQL for MySQL

Cloud 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

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 MySQL

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.

Cloud SQL for PostgreSQL

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 Server

Cloud 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 MySQL

Cloud 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:

To get started using MySQL 8.0 on Cloud SQL, see Creating instances.

July 09, 2020

Cloud SQL for PostgreSQL

Cloud 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 MySQL

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.

Cloud SQL for PostgreSQL

Cloud SQL for SQL Server

June 08, 2020

Cloud SQL for MySQL

Support for asia-southeast2 region (Jakarta).

Cloud SQL for PostgreSQL

Support for asia-southeast2 region (Jakarta).

Cloud SQL for SQL Server

Support for asia-southeast2 region (Jakarta).

May 21, 2020

Cloud SQL for PostgreSQL

PostgreSQL version 12 is now generally available. To start using PostgreSQL 12, see Creating instances.

May 18, 2020

Cloud SQL for MySQL

MySQL 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 PostgreSQL

PostgreSQL 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 PostgreSQL

Cloud 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

Cloud SQL for SQL Server

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 MySQL

MySQL 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 MySQL

Support for us-west3 region (Salt Lake City).

Cloud SQL for PostgreSQL

Support for us-west3 region (Salt Lake City).

Cloud SQL for SQL Server

Support for us-west3 region (Salt Lake City).

February 19, 2020

Cloud SQL for SQL Server

Cloud 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 MySQL

First 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 PostgreSQL

PostgreSQL version 10 is now Beta. To start using PostgreSQL 10, see Creating Instances.

January 24, 2020

Cloud SQL for MySQL

Support for asia-northeast3 region (Seoul).

Cloud SQL for PostgreSQL

Support for asia-northeast3 region (Seoul).

Cloud SQL for SQL Server

Support for asia-northeast3 region (Seoul).

December 17, 2019

Cloud SQL for MySQL

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 for PostgreSQL

Cloud SQL for SQL Server

December 13, 2019

Cloud SQL for MySQL

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.

Cloud SQL for PostgreSQL

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

Cloud SQL for SQL Server

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

December 10, 2019

Cloud SQL for MySQL

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 for PostgreSQL

Cloud SQL for SQL Server

November 25, 2019

Cloud SQL for MySQL

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 for PostgreSQL

Cloud SQL for SQL Server

November 19, 2019

Cloud SQL for MySQL

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 for PostgreSQL

Cloud SQL for SQL Server

October 18, 2019

Cloud SQL for MySQL

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

Cloud SQL for SQL Server

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

Cloud SQL for MySQL

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

Cloud SQL for PostgreSQL

Cloud SQL for PostgreSQL

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 for MySQL

Cloud 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 MySQL

GA support for Private IP connectivity.

Cloud SQL for PostgreSQL

GA support for Private IP connectivity.

November 06, 2018

Cloud SQL for PostgreSQL

Support for CSV format for PostgreSQL instance imports and exports.

October 01, 2018

Cloud SQL for MySQL

Support for asia-east2 region (Hong Kong).

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

Cloud SQL for PostgreSQL

Support for asia-east2 region (Hong Kong).

September 01, 2018

Cloud SQL for MySQL

Cloud SQL for MySQL

MySQL 5.6 minor version upgraded to 5.6.36.

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

Cloud SQL for PostgreSQL

MySQL 5.6 minor version upgraded to 5.6.36.

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

Cloud SQL for MySQL

Support for europe-west3 region (Frankfurt).

Cloud SQL for PostgreSQL

Support for europe-west3 region (Frankfurt).

June 01, 2017

Cloud SQL for MySQL

Support for labels.

Proxy version 1.10 released.

Support for australia-southeast1 region (Sydney).

Support for europe-west2 region (London).

Cloud SQL for PostgreSQL

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 MySQL

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).

Cloud SQL for PostgreSQL

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).