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.

September 08, 2025

Cloud SQL for PostgreSQL

You can have Cloud SQL create a Private Service Connect endpoint automatically. You can use this endpoint to access Cloud SQL instances through a VPC network. For more information, see Create a Private Service Connect endpoint automatically.

This feature is now generally available (GA).

September 04, 2025

Cloud SQL for MySQL

The release note on August 13, 2025 regarding Private Service Connect (PSC) outbound connectivity has been updated.

PSC outbound connectivity is required for homogeneous migrations to PSC-enabled Cloud SQL instances using Database Migration Service. For more information, see PSC outbound connections.

Cloud SQL for PostgreSQL

The release note on August 13, 2025 regarding Private Service Connect (PSC) outbound connectivity has been updated.

PSC outbound connectivity is required for homogeneous migrations to PSC-enabled Cloud SQL instances using Database Migration Service. For more information, see PSC outbound connections.

September 03, 2025

Cloud SQL for MySQL

Cloud SQL Managed Connection Pooling is now generally available (GA). Managed Connection Pooling lets you scale your workloads by optimizing resource utilization for Cloud SQL instances using pooling.

For more information, see Managed Connection Pooling overview.

You can now enable your instance to take a final backup at instance deletion and define its retention period by setting the final backup instance setting.

You can also create a custom organization policy to define final backup instance settings. For more information, see Final backup.

Cloud SQL for PostgreSQL

You can now enable your instance to take a final backup at instance deletion and define its retention period by setting the final backup instance setting.

You can also create a custom organization policy to define final backup instance settings. For more information, see Final backup.

Cloud SQL for SQL Server

You can now enable your instance to take a final backup at instance deletion and define its retention period by setting the final backup instance setting.

You can also create a custom organization policy to define final backup instance settings. For more information, see Final backup.

August 29, 2025

Cloud SQL for SQL Server

Max degree of parallelism (MAXDOP) is a Microsoft database flag available for use in Cloud SQL for SQL Server. This flag lets you limit the maximum number of threads used when running a single query in a parallel plan.

August 21, 2025

Cloud SQL for MySQL

You can save and manage SQL queries in Cloud SQL Studio. This feature is in Preview. For more information, see Saved queries overview.

Cloud SQL for PostgreSQL

You can save and manage SQL queries in Cloud SQL Studio. This feature is in Preview. For more information, see Saved queries overview.

Cloud SQL for SQL Server

You can save and manage SQL queries in Cloud SQL Studio. This feature is in Preview. For more information, see Saved queries overview.

August 15, 2025

Cloud SQL for MySQL

Now you can use Private Service Connect backends, as an alternative to Private Service Connect endpoints, to access Cloud SQL instances.

Now you can create an IPv6 endpoint for Private Service Connect (PSC) connections. For more information, see Connect to an instance using Private Service Connect.

You can no longer set a deny maintenance period for instances that are running a maintenance version older than 12 months. To update your instance, perform self-service maintenance or wait until the next maintenance window to update your instance automatically. For more information about maintenance, see Maintenance updates on Cloud SQL instances.

Cloud SQL for PostgreSQL

Now you can use Private Service Connect backends, as an alternative to Private Service Connect endpoints, to access Cloud SQL instances.

Now you can create an IPv6 endpoint for Private Service Connect (PSC) connections. For more information, see Connect to an instance using Private Service Connect.

You can no longer set a deny maintenance period for instances that are running a maintenance version older than 12 months. To update your instance, perform self-service maintenance or wait until the next maintenance window to update your instance automatically. For more information about maintenance, see Maintenance updates on Cloud SQL instances.

Cloud SQL for SQL Server

Now you can use Private Service Connect backends, as an alternative to Private Service Connect endpoints, to access Cloud SQL instances.

Now you can create an IPv6 endpoint for Private Service Connect (PSC) connections. For more information, see Connect to an instance using Private Service Connect.

You can no longer set a deny maintenance period for instances that are running a maintenance version older than 12 months. To update your instance, perform self-service maintenance or wait until the next maintenance window to update your instance automatically. For more information about maintenance, see Maintenance updates on Cloud SQL instances.

August 13, 2025

Cloud SQL for MySQL

Cloud SQL now supports Private Service Connect (PSC) outbound connectivity. With PSC outbound connectivity, you can attach a PSC interface to your existing Cloud SQL PSC-enabled instances to allow your instances to make outbound connections to your network. This is required for homogeneous migrations to PSC-enabled Cloud SQL instances using Database Migration Service. For more information, see PSC outbound connections.

Cloud SQL for PostgreSQL

Cloud SQL now supports Private Service Connect (PSC) outbound connectivity. With PSC outbound connectivity, you can attach a PSC interface to your existing Cloud SQL PSC-enabled instances to allow your instances to make outbound connections to your network. This is required for homogeneous migrations to PSC-enabled Cloud SQL instances using Database Migration Service. For more information, see PSC outbound connections.

Cloud SQL for SQL Server

Cloud SQL now supports Private Service Connect (PSC) outbound connectivity. With PSC outbound connectivity, you can attach a PSC interface to your existing Cloud SQL PSC-enabled instances to allow your instances to make outbound connections to your network. For more information, see PSC outbound connections.

August 07, 2025

Cloud SQL for MySQL

Cloud SQL for Enterprise Plus edition supports quality enhancements for AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition.

Cloud SQL for PostgreSQL

Cloud SQL for Enterprise Plus edition supports quality enhancements for AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition.

Cloud SQL for SQL Server

Cloud SQL now offers planned maintenance and machine tier upgrades for your Cloud SQL Enterprise plus instances with near-zero downtime for eligible instances.

For more information, see Maintenance updates on Cloud SQL instances.

August 04, 2025

Cloud SQL for MySQL

Cloud SQL for MySQL now supports model endpoint management to help you build your generative AI applications. With model endpoint management, you can register and call remote AI model providers or access the Vertex AI integration. This feature is in Preview and available in Cloud SQL for MySQL version 8.0.36 and later, which includes Cloud SQL for MySQL version 8.4.

To use model endpoint management, update your instance to [MySQL version].R20250531.01_14 or later, and make sure that you've enabled the integration with Vertex AI on your instance. You can perform self-service maintenance or wait until the next maintenance window to update the maintenance version of your instance automatically.

Cloud SQL for PostgreSQL

PostgreSQL has identified a bug in PostgreSQL's May 8, 2025 release that is causing logical replication to halt. Cloud SQL for PostgreSQL released [PostgreSQL version].R20250302.00_19 on May 22, 2025, which is impacted by this bug.

If you use logical replication with your Cloud SQL for PostgreSQL instances, then we recommend that you don't update your instances to this version or any self-service maintenance version released after May 22, 2025, due to this PostgreSQL bug. We also recommend not performing a major version upgrade on your instances, since it adopts the latest self-service maintenance version.

We expect a fix for this issue in the next automatically-scheduled maintenance. For more information about this bug, see Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5.

July 31, 2025

Cloud SQL for MySQL

Cloud SQL now offers two options of backup services to manage your instance's backups:

  • Enhanced backups (Preview): backups are managed and stored in a centralized backup management project that leverages the Backup and DR service, and provides enforced retention, granular scheduling, and longer retention.

  • Standard backups (existing option): backups are created, managed, and stored in the same project as your Cloud SQL instances.

You can choose between these options based on your instance's requirements and needs. Although instances can't use both backup options at the same time, Cloud SQL gives you the ability to switch between these backup options as necessary.

For more information about the available options and their limitations, see Backup options.

Cloud SQL for PostgreSQL

Cloud SQL now offers two options of backup services to manage your instance's backups:

  • Enhanced backups (Preview): backups are managed and stored in a centralized backup management project that leverages the Backup and DR service, and provides enforced retention, granular scheduling, and longer retention.

  • Standard backups (existing option): backups are created, managed, and stored in the same project as your Cloud SQL instances.

You can choose between these options based on your instance's requirements and needs. Although instances can't use both backup options at the same time, Cloud SQL gives you the ability to switch between these backup options as necessary.

For more information about the available options and their limitations, see Backup options.

Cloud SQL for SQL Server

Cloud SQL now offers two options of backup services to manage your instance's backups:

  • Enhanced backups (Preview): backups are managed and stored in a centralized backup management project that leverages the Backup and DR service, and provides enforced retention, granular scheduling, and longer retention.

  • Standard backups (existing option): backups are created, managed, and stored in the same project as your Cloud SQL instances.

You can choose between these options based on your instance's requirements and needs. Although instances can't use both backup options at the same time, Cloud SQL gives you the ability to switch between these backup options as necessary.

For more information about the available options and their limitations, see Backup options.

July 08, 2025

Cloud SQL for SQL Server

Cloud SQL for SQL Server now offers Active Directory support for write endpoints. For more information, see Write endpoints across forests.

July 02, 2025

Cloud SQL for MySQL

The write endpoint feature for Cloud SQL Enterprise Plus edition instances is now generally available (GA). This endpoint is a global domain name service (DNS) name and resolves to the IP address of the current primary Cloud SQL instance that's enabled with private services access.

By using a write endpoint, you can avoid having to make application connection changes after performing a switchover or replica failover operation to test or mitigate a region failure.

For more information, see Connect to an instance using a write endpoint.

Cloud SQL for PostgreSQL

The write endpoint feature for Cloud SQL Enterprise Plus edition instances is now generally available (GA). This endpoint is a global domain name service (DNS) name and resolves to the IP address of the current primary Cloud SQL instance that's enabled with private services access.

By using a write endpoint, you can avoid having to make application connection changes after performing a switchover or replica failover operation to test or mitigate a region failure.

For more information, see Connect to an instance using a write endpoint.

June 24, 2025

Cloud SQL for MySQL

Cloud SQL for MySQL 8.4.4 is upgraded to MySQL 8.4.5. For more information, see the MySQL 8.4.5 Release Notes.

June 17, 2025

Cloud SQL for MySQL

You no longer have to upgrade your instance to MySQL 8.0.37 before you upgrade to Cloud SQL for MySQL 8.4. You can upgrade to Cloud SQL for MySQL 8.4 from any minor version of Cloud SQL for MySQL 8.0. For more information about upgrading the major version of a Cloud SQL instance, see Upgrade the database major version-place.

May 28, 2025

Cloud SQL for SQL Server

Cloud SQL for SQL Server now offers the maximum server memory recommender.

Database instances running with an allocation of memory that's either too low or too high might experience performance issues.

The max server memory (mb) flag limits the amount of memory that Cloud SQL can allocate for its internal pools. You can manually set a value for this flag, or omit the flag and let Cloud SQL manage memory limits for you automatically.

For more information, see Optimize maximum server memory usage.

May 23, 2025

Cloud SQL for SQL Server

Cloud SQL for SQL Server now extends query insights and index advisor support to read replicas.

May 22, 2025

Cloud SQL for MySQL

You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).

For more information, see Configure both private services access and Private Service Connect.

Cloud SQL for PostgreSQL

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

Minor versions

  • 13.20 is upgraded to 13.21.
  • 14.17 is upgraded to 14.18.
  • 15.12 is upgraded to 15.13.
  • 16.8 is upgraded to 16.9.
  • 17.4 is upgraded to 17.5.

Extensions and plugins

  • pg_squeeze is upgraded from 1.5 to 1.8 for all PostgreSQL versions 12 and above.

To use these versions of the extensions, update your instance to [PostgreSQL version].R20250302.00_19.

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.

For more information on checking 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 create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).

For more information, see Configure both private services access and Private Service Connect.

Cloud SQL for SQL Server

You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).

For more information, see Configure both private services access and Private Service Connect.

May 15, 2025

Cloud SQL for MySQL

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

You can now use advanced disaster recovery (DR) for your Private Service Connect (PSC) enabled Cloud SQL Enterprise Plus edition instances. With advanced DR, you can:

  • Designate a cross-region disaster recovery (DR) replica
  • Perform a cross-region replica failover for disaster recovery
  • 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 Use advanced disaster recovery (DR). This feature is generally available (GA).

Cloud SQL for PostgreSQL

You can now use advanced disaster recovery (DR) for your Private Service Connect (PSC) enabled Cloud SQL Enterprise Plus edition instances. With advanced DR, you can:

  • Designate a cross-region disaster recovery (DR) replica
  • Perform a cross-region replica failover for disaster recovery
  • 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 Use advanced disaster recovery (DR). This feature is generally available (GA).

May 14, 2025

Cloud SQL for SQL Server

Cloud SQL for SQL Server now supports TLS connections to Active Directory endpoints without requiring server certificate trust or the use of IP addresses. Existing server certificates will need to be rotated to use this feature.

May 08, 2025

Cloud SQL for MySQL

If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.

For users of the Cloud SQL Auth Proxy:

  • If the Cloud SQL instance to which you're connecting is using shared certificate authority (CA) for its serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later.
  • If the Cloud SQL instance to which you're connecting is using customer-managed CA for its serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.
Cloud SQL for PostgreSQL

If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.

For users of the Cloud SQL Auth Proxy:

  • If the Cloud SQL instance to which you're connecting is using shared certificate authority (CA) for its serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later.
  • If the Cloud SQL instance to which you're connecting is using customer-managed CA for its serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.
Cloud SQL for SQL Server

If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.

For users of the Cloud SQL Auth Proxy:

  • If the Cloud SQL instance to which you're connecting is using shared certificate authority (CA) for its serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later.
  • If the Cloud SQL instance to which you're connecting is using customer-managed CA for its serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.

May 07, 2025

Cloud SQL for PostgreSQL

You can migrate to AlloyDB for PostgreSQL using your Cloud SQL for PostgreSQL backup (GA). The Google Cloud CLI is also supported. For more information, see Migrate from Cloud SQL for PostgreSQL to AlloyDB.

May 05, 2025

Cloud SQL for SQL Server

Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.

May 02, 2025

Cloud SQL for MySQL

You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.

Custom SAN configuration for instances is generally available (GA).

Cloud SQL for PostgreSQL

You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.

Custom SAN configuration for instances is generally available (GA).

Cloud SQL for SQL Server

You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.

Custom SAN configuration for instances is generally available (GA).

May 01, 2025

Cloud SQL for MySQL

Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.

You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA), the shared CA (GOOGLE_MANAGED_CAS_CA), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) is the default configuration.

The shared CA and customer-managed CA options are now generally available (GA).

Cloud SQL for PostgreSQL

Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.

You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA), the shared CA (GOOGLE_MANAGED_CAS_CA), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) is the default configuration.

The shared CA and customer-managed CA options are now generally available (GA).

Cloud SQL for SQL Server

Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.

You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA), the shared CA (GOOGLE_MANAGED_CAS_CA), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) is the default configuration.

The shared CA and customer-managed CA options are now generally available (GA).

April 30, 2025

Cloud SQL for PostgreSQL

The rollout of the following extension versions and plugin versions is complete:

Extensions and plugins

  • pg_partman is upgraded from 5.0.1 to 5.2.4 (for PostgreSQL versions 14 and later).

To use this version of the extension, update your instance to [PostgreSQL version].R20250302.00_10.

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.

For more information on checking your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

April 24, 2025

Cloud SQL for MySQL

Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.

Cloud SQL for PostgreSQL

Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.

Cloud SQL for SQL Server

Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.

April 18, 2025

Cloud SQL for MySQL

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

April 09, 2025

Cloud SQL for MySQL

Cloud SQL Enterprise Plus edition now supports a new machine series called the C4A machine series, which provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. C4A uses a new type of storage called Hyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available in Preview.

For more information about the C4A machine series and its availability, see Machine series overview.

Query insights for Cloud SQL Enterprise Plus edition is now generally available (GA) for your Cloud SQL Enterprise Plus edition for MySQL instances. Query insights for Cloud SQL Enterprise Plus edition offers fine-grained metrics such as wait events and granular query plan samples for faster root-cause analysis and intelligent index recommendations.

For more information, see Use query insights to improve query performance.

Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.

Cloud SQL for PostgreSQL

Cloud SQL Enterprise Plus edition now supports a new machine series called the C4A machine series, which provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. C4A uses a new type of storage called Hyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available in Preview.

For more information about the C4A machine series and its availability, see Machine series overview.

Query insights for Cloud SQL Enterprise Plus edition is now generally available (GA) for your Cloud SQL Enterprise Plus edition for PostgreSQL instances. Query insights for Cloud SQL Enterprise Plus edition offers fine-grained metrics such as wait events and granular query plan samples for faster root-cause analysis and intelligent index recommendations.

For more information, see Use query insights to improve query performance.

Cloud SQL for Enterprise Plus edition supports