Cloud SQL release notes

You can use the pg_textsearch extension in Cloud SQL for PostgreSQL to perform full-text search using the industry-standard BM25 (Best Matching 25) scoring algorithm for highly accurate relevance scoring.

This extension requires PostgreSQL 17 or later and is supported on PostgreSQL release R20260712.01_06 or later.

For more information, see Full-text search using pg_textsearch.

Beginning April 12, 2027, you won't be able to create new instances of Cloud SQL for SQL Server 2017. Starting on October 13, 2027, SQL Server 2017 will reach end of life (EOL) and Microsoft will stop releasing security updates. Cloud SQL for SQL Server will stop supporting SQL Server 2017 after this date.

For more information, see Database versions and version policies.

Appending sqlcommenter tags using the sql_commenter_enabled parameter when executing SQL queries on a Cloud SQL remote MCP server is temporarily disabled.

For more information, see sqlcommenter tags.

Appending sqlcommenter tags using the sql_commenter_enabled parameter when executing SQL queries on a Cloud SQL remote MCP server is temporarily disabled.

For more information, see sqlcommenter tags.

Regional endpoints (REP) are now generally available (GA) for the Cloud SQL for MySQL Admin API.

Regional endpoints let you interact with Cloud SQL for MySQL instances using regionalized URLs (such as sqladmin.{region}.rep.googleapis.com) rather than through a single global endpoint.

Regional endpoints provide regional frontend and load balancing infrastructure that improves data residency by keeping network traffic within the same region as the instance. This reduces the instance's dependency on global frontend infrastructure.

Regional endpoints have strong regional isolation, so the failure of a load balancer or frontend in one region doesn't affect any other region. Regional service load balancers have a separate, regionally isolated control plane.

Regional endpoints are designed to meet stringent data residency and sovereignty standards, such as ITAR and Assured Workloads Regions, ensuring data in transit remains within the committed region.

Certificate management and TLS termination occurs within each region, on the regional load balancer, so data remains encrypted until it reaches its destination region and stays within that region while being processed there.

Regional endpoints (REP) are now generally available (GA) for the Cloud SQL for PostgreSQL Admin API.

Regional endpoints let you interact with Cloud SQL for PostgreSQL instances using regionalized URLs (such as sqladmin.{region}.rep.googleapis.com) rather than through a single global endpoint.

Regional endpoints provide regional frontend and load balancing infrastructure that improves data residency by keeping network traffic within the same region as the instance. This reduces the instance's dependency on global frontend infrastructure.

Regional endpoints have strong regional isolation, so the failure of a load balancer or frontend in one region doesn't affect any other region. Regional service load balancers have a separate, regionally isolated control plane.

Regional endpoints are designed to meet stringent data residency and sovereignty standards, such as ITAR and Assured Workloads Regions, ensuring data in transit remains within the committed region.

Certificate management and TLS termination occurs within each region, on the regional load balancer, so data remains encrypted until it reaches its destination region and stays within that region while being processed there.

Regional endpoints (REP) are now generally available (GA) for the Cloud SQL for SQL Server Admin API.

Regional endpoints let you interact with Cloud SQL for SQL Server instances using regionalized URLs (such as sqladmin.{region}.rep.googleapis.com) rather than through a single global endpoint.

Regional endpoints provide regional frontend and load balancing infrastructure that improves data residency by keeping network traffic within the same region as the instance. This reduces the instance's dependency on global frontend infrastructure.

Regional endpoints have strong regional isolation, so the failure of a load balancer or frontend in one region doesn't affect any other region. Regional service load balancers have a separate, regionally isolated control plane.

Regional endpoints are designed to meet stringent data residency and sovereignty standards, such as ITAR and Assured Workloads Regions, ensuring data in transit remains within the committed region.

Certificate management and TLS termination occurs within each region, on the regional load balancer, so data remains encrypted until it reaches its destination region and stays within that region while being processed there.

The C4 machine series is now available for Cloud SQL for MySQL Enterprise Plus instances in the following regions:

• africa-south1 — Johannesburg
• asia-northeast3 — Seoul
• asia-south2 — Delhi
• europe-west6 — Zürich
• southamerica-west1 — Santiago
• us-west3 — Salt Lake City

The C4 machine series provides the following benefits:

• Supports fifth and sixth generation Intel Xeon Scalable processors.
• Offers a price-performance balance that makes it suitable for high-demand workloads.

Cloud SQL supports in-place upgrades and downgrades to your instance's infrastructure. You can change all of the following in place:

• The edition that your Cloud SQL instance uses.
• The machine type.
• The storage type.
• The database version.

Making in-place changes is the most direct and least error-prone way to reconfigure an instance.

For more information about in-place upgrades and downgrades, see Upgrade in place.

The C4 machine series is now available for Cloud SQL for PostgreSQL Enterprise Plus instances in the following regions:

• africa-south1 — Johannesburg
• asia-northeast3 — Seoul
• asia-south2 — Delhi
• europe-west6 — Zürich
• southamerica-west1 — Santiago
• us-west3 — Salt Lake City

The C4 machine series provides the following benefits:

• Supports fifth and sixth generation Intel Xeon Scalable processors.
• Offers a price-performance balance that makes it suitable for high-demand workloads.

Cloud SQL supports in-place upgrades and downgrades to your instance's infrastructure. You can change all of the following in place:

• The edition that your Cloud SQL instance uses.
• The machine type.
• The storage type.
• The database version.

Making in-place changes is the most direct and least error-prone way to reconfigure an instance.

For more information about in-place upgrades and downgrades, see Upgrade in place.

Cloud SQL for SQL Server now supports connecting to instances with write endpoints using the Cloud SQL Auth Proxy or Cloud SQL language connectors. When you configure the proxy or a language connector with a write endpoint DNS name, connections are redirected automatically to the new primary instance during replica failover or switchover.

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

The C4 machine series is now available for Cloud SQL for SQL Server Enterprise Plus instances in the following regions:

• africa-south1 — Johannesburg
• asia-northeast3 — Seoul
• asia-south2 — Delhi
• europe-west6 — Zürich
• southamerica-west1 — Santiago
• us-west3 — Salt Lake City

The C4 machine series provides the following benefits:

• Supports fifth and sixth generation Intel Xeon Scalable processors.
• Offers a price-performance balance that makes it suitable for high-demand workloads.

Cloud SQL supports in-place upgrades and downgrades to your instance's infrastructure. You can change all of the following in place:

• The edition that your Cloud SQL instance uses.
• The machine type.
• The storage type.
• The database version.

Making in-place changes is the most direct and least error-prone way to reconfigure an instance.

For more information about in-place upgrades and downgrades, see Upgrade in place.

Cloud SQL supports Workforce Identity Federation authentication. This lets you authenticate to your Cloud SQL instance using identities from an external identity provider such as Microsoft Active Directory or Okta. For more information, see Workforce Identity Federation authentication.

Cloud SQL supports Workforce Identity Federation authentication. This lets you authenticate to your Cloud SQL instance using identities from an external identity provider such as Microsoft Active Directory or Okta. For more information, see Workforce Identity Federation authentication.

You can use the pgAudit extension to prevent string literals that might indicate sensitive information, such as passwords and secrets, from appearing in your log query results.

This pgAudit extension capability is supported on [PostgreSQL version].R20260712.01_06 or later.

For more information, see Audit for PostgreSQL using pgAudit.

Cloud SQL now makes it easier to configure Private Service Connect for your Cloud SQL instance. When you create an instance that's enabled with Private Service Connect, you can choose to automatically create the service connection policy and endpoint in the VPC network that you want to use with Private Service Connect.

For more information, see Configure Private Service Connect.

The rollout of the following extension upgrades is complete:

• pg_partman is upgraded from 5.2.4 to 5.4.3.
• pgfincore is upgraded from 1.3.1 to 1.4.
• pgvector is upgraded from 0.8.1 to 0.8.5.

For more information, see Configure PostgreSQL extensions.

Cloud SQL now makes it easier to configure Private Service Connect for your Cloud SQL instance. When you create an instance that's enabled with Private Service Connect, you can choose to automatically create the service connection policy and endpoint in the VPC network that you want to use with Private Service Connect.

For more information, see Configure Private Service Connect.

Cloud SQL now makes it easier to configure Private Service Connect for your Cloud SQL instance. When you create an instance that's enabled with Private Service Connect, you can choose to automatically create the service connection policy and endpoint in the VPC network that you want to use with Private Service Connect.

For more information, see Configure Private Service Connect.

Use assessments (Preview) in Database Center to assess and test the performance impact of database recommendations before you apply them to your production database fleet.

The assessments workflow performs these operations:

• Clones your database instance.
• Runs benchmarking simulation tests on the clone.
• Compares the baseline performance of the clone against the performance after you apply the recommended configuration changes.

For more information, see Assessments in Database Center.

Cloud SQL for MySQL 9.7 is generally available (GA).

For more information about the differences between MySQL 9.7 and previous versions, review the MySQL 9.7 Release Notes.

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

This release introduces support for key MySQL 9.7 capabilities, including:

• Vector search: support for the community-standard vector storage format combined with advanced approximate nearest neighbor (ANN) vector indexing in Cloud SQL.
• Hypergraph optimizer: an alternative join-planning framework designed for complex, multi-table queries. You can enable the hypergraph optimizer using an optimizer switch.
• JSON Duality Views: a feature that bridges relational SQL and hierarchical JSON document models to interact with the same underlying data.
• Upgrade and migration paths: support for in-place major version upgrade from Cloud SQL for MySQL 8.4 and migrations from MySQL 8.4 using the Database Migration Service (DMS).

Flag updates for MySQL 9.7

Additionally, this release introduces several database flag changes.

For more information about MySQL database flags, see Configure database flags.

The Cloud SQL remote MCP server now supports specialized endpoint URLs (toolsets) for /readonly, /instance_manage, and /query_execution. Specialized toolset URLs let you restrict the set of exposed MCP tools based on your security and workflow requirements.

For more information, see Available toolsets.

You can now use the create_instance tool in the Cloud SQL remote MCP server to provision free trial instances for testing and development by setting the free_trial parameter to true.

For more information, see Create a free trial instance.

When executing SQL queries using the execute_sql or execute_sql_readonly tool, setting the sql_commenter_enabled parameter to true automatically appends sqlcommenter tags (mcp.tool, mcp.server, user.identity, mcp.client) to SQL statements for enhanced database observability.

For more information, see sqlcommenter tags.

The Cloud SQL remote MCP server now supports specialized endpoint URLs (toolsets) for /readonly, /instance_manage, and /query_execution. Specialized toolset URLs let you restrict the set of exposed MCP tools based on your security and workflow requirements.

For more information, see Available toolsets.

You can now use the create_instance tool in the Cloud SQL remote MCP server to provision free trial instances for testing and development by setting the free_trial parameter to true.

For more information, see Create a free trial instance.

When executing SQL queries using the execute_sql or execute_sql_readonly tool, setting the sql_commenter_enabled parameter to true automatically appends sqlcommenter tags (mcp.tool, mcp.server, user.identity, mcp.client) to SQL statements for enhanced database observability.

For more information, see sqlcommenter tags.

You can now use the update_user tool in the Cloud SQL remote MCP server to update passwords for Cloud SQL for SQL Server database users.

For more information, see Available tools.

The Cloud SQL remote MCP server now supports specialized endpoint URLs (toolsets) for /readonly and /instance_manage. Specialized toolset URLs let you restrict the set of exposed MCP tools based on your security and workflow requirements.

For more information, see Available toolsets.

Newly created instances configured with high availability (HA) now have Knowledge Catalog (formerly Dataplex Universal Catalog) enabled by default.

Cloud SQL for PostgreSQL instances running on PostgreSQL version 14.0 or later send updates and metadata to Knowledge Catalog in near real-time.

You can either verify enablement or disable the feature using the Google Cloud console.

For more information, see Near real-time.

Newly created instances configured with high availability (HA) now have Knowledge Catalog (formerly Dataplex Universal Catalog) enabled by default.

Cloud SQL for SQL Server instances send updates and metadata to Knowledge Catalog to help support data discovery.

You can either verify enablement or disable the feature using the Google Cloud console.

For more information, see Manage your Cloud SQL resources using Knowledge Catalog.

Performance capture for Cloud SQL for MySQL is now generally available (GA). Performance capture lets you take a point-in-time snapshot of your database and operating system metrics automatically and route them to Cloud Logging for root-cause analysis.

With the GA release, you can configure custom thresholds that end long-running transactions automatically before they slow down your database. In addition, the GA release includes six additional performance capture triggers:

• High CPU utilization
• High memory usage
• High temporary files usage
• History list length
• Semaphore waits
• Transaction lock waits

For more information, see Cloud SQL performance capture overview.

DNS automation is now generally available (GA) on Cloud SQL instances where Private Service Connect is enabled.

You can use DNS automation to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

Cloud SQL for MySQL supports resource groups. MySQL resource groups let you manage resource allocation for different workloads on your Cloud SQL for MySQL instance. By using resource groups, you can prevent less important workloads from consuming excessive CPU or memory resources.

To use MySQL resource groups, you must have maintenance version MYSQL_VERSION.R20260320.00_20 or later installed on your instance.

For more information, see Manage CPU allocation with MySQL resource groups.

DNS automation is now generally available (GA) on Cloud SQL instances where Private Service Connect is enabled.

You can use DNS automation to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

DNS automation is now generally available (GA) on Cloud SQL instances where Private Service Connect is enabled.

You can use DNS automation to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

You can change the backup plan for your Cloud SQL enhanced backups without first removing the existing plan. For more information, see Change your instance's associated backup plan.

You can change the backup plan for your Cloud SQL enhanced backups without first removing the existing plan. For more information, see Change your instance's associated backup plan.

You can change the backup plan for your Cloud SQL enhanced backups without first removing the existing plan. For more information, see Change your instance's associated backup plan.

Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled.

When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those endpoints.

For more information, see Allowed Private Service Connect projects.

QueryData adds support for parameterized secure views (PSVs) to help secure applications that use natural language queries. For more information, see Secure and control access to application data.

This feature is in Preview.

Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled.

When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those endpoints.

For more information, see Allowed Private Service Connect projects.

Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled.

When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those endpoints.

For more information, see Allowed Private Service Connect projects.

Cloud SQL for SQL Server now supports executing SQL statements using the Cloud SQL Data API.

Cloud SQL for MySQL now supports significantly faster re-encryption of instances and replicas protected by customer-managed encryption keys (CMEKs), and re-encryption now completes with zero downtime. The steps to re-encrypt your instances and replicas are unchanged, but the operation now re-encrypts the underlying disks in-place, without creating re-encryption backups.

For more information, see Re-encrypt an existing CMEK-enabled instance or replica.