You can now assign database roles to built-in database users and IAM database users when you create or update users. For more information about assigning roles, see built-in database authentication or IAM database authentication.
You can now assign database roles to built-in database users and IAM database users when you create or update users. For more information about assigning roles, see built-in database authentication or IAM database authentication.
]]>Cloud SQL for MySQL now supports performance capture to help you diagnose transient performance issues with your MySQL database. Performance capture lets you specify configurable thresholds for additional monitoring. If a threshold is reached, then performance capture takes snapshots of the database state, including in-flight transactions, InnoDB status, and, in the case of replication lag, detailed replication status. Performance capture outputs the snapshots in a log format so you can review the state of the instance when the problem occurred.
For more information, see Cloud SQL performance capture overview. Performance capture is in Preview.
]]>Cloud SQL for MySQL 8.0.43 is now the default minor version of Cloud SQL for MySQL 8.0.
If you have automatic minor version upgrade enabled for your instance, then your instance is upgraded to the default minor version automatically during its regularly scheduled maintenance update.
For more information about automatic minor version upgrade, see Upgrade the database minor version of MySQL 8.0.
]]>Cloud SQL for MySQL now supports fast clone operations within the same zone (GA).
For more information, see Clone an instance.
Cloud SQL for PostgreSQL now supports fast clone operations within the same zone (GA).
For more information, see Clone an instance.
]]>You can build data agents that interact with the data in your database using conversational language. Use these data agents as tools to empower your applications. For more information, see Data agents overview. This feature is available in Preview, and access to it requires a sign-up.
You can build data agents that interact with the data in your database using conversational language. Use these data agents as tools to empower your applications. For more information, see Data agents overview. This feature is available in Preview, and access to it requires a sign-up.
]]>Cloud SQL enhanced backups are now generally available (GA).
With enhanced backups, 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.
Enhanced backups now also support point-in-time-recovery (PITR) after instance deletion.
For more information about the available options and their limitations, see Backup options. For more information about enhanced backups pricing, see Backup and DR pricing.
Cloud SQL enhanced backups are now generally available (GA).
With enhanced backups, 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.
Enhanced backups now also support point-in-time-recovery (PITR) after instance deletion.
For more information about the available options and their limitations, see Backup options. For more information about enhanced backups pricing, see Backup and DR pricing.
Cloud SQL enhanced backups are now generally available (GA).
With enhanced backups, 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.
Enhanced backups now also support point-in-time-recovery (PITR) after instance deletion.
For more information about the available options and their limitations, see Backup options. For more information about enhanced backups pricing, see Backup and DR pricing.
]]>Cloud SQL for SQL Server integration with Microsoft Entra ID (Preview) provides centralized identity and access management (IAM) for your databases using your existing Microsoft Entra ID tenant.
]]>To help prevent out-of-memory (OOM) events, you can enable managed buffer pool
for Cloud SQL for MySQL 8.0 and later instances. When you enable managed buffer
pool, Cloud SQL reduces the value of the
innodb_buffer_pool_size configuration and frees up memory when memory usage
is high, and the instance is in danger of an OOM event.
After memory usage stabilizes at a lower value, MySQL increases the
value of innodb_buffer_pool_size incrementally to its original value.
To enable managed buffer pool, your Cloud SQL instance must use a
maintenance version of [$MYSQL_VERSION].R20251004.01_07
or later. You can't enable managed buffer pool for instances that use a
shared core or for instances that are running MySQL 5.6 or MySQL 5.7.
For more information, see Enable managed buffer pool. Support for managed buffer pool is in Preview.
]]>PostgreSQL version 18 is now generally available for Cloud SQL for PostgreSQL.
You can now use Database Migration Service with Cloud SQL for PostgreSQL when using PostgreSQL version 18.
To upgrade your instance to PostgreSQL 18, see Upgrade the database major version in-place.
The following extensions are also now available for PostgreSQL 18:
pg_hint_planpgroutinganonymizerpg_wait_samplingtds_fdwplpgsql_checkFor more information about these extensions, see Configure PostgreSQL extensions.
]]>The rollout of the following minor version and extension upgrades is complete:
Minor versions
Extensions
Pgvector is upgraded from 0.8.0 to 0.8.1.To use these versions of the extensions and plugins, update your instance to
[PostgreSQL version].R20251004.01_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.
Cloud SQL for PostgreSQL now supports Vector assist (Preview).
Vector assist is a Cloud SQL for PostgreSQL extension that simplifies the deployment and management of your Cloud SQL vector workloads. It helps you set up production-ready vector search capabilities, such as embedding generation, query optimization, and index creation.
For more information about vector assist, how it works, and its limitations, see Vector assist overview.
]]>Cloud SQL for MySQL 8.4.6 is upgraded to MySQL 8.4.7. For more information, see the MySQL 8.4.7 Release Notes.
]]>Cloud SQL now offers a free trial instance for both existing and new Google Cloud customers. A free trial instance lets you test advanced Cloud SQL capabilities and features for up to 30 days without any financial commitment.
For information about a free trial instance, and its inclusions and conditions, see Free trial instance overview.
Cloud SQL now offers a free trial instance for both existing and new Google Cloud customers. A free trial instance lets you test advanced Cloud SQL capabilities and features for up to 30 days without any financial commitment.
For information about a free trial instance, and its inclusions and conditions, see Free trial instance overview.
]]>Cloud SQL for MySQL now supports read pool autoscaling (GA), which helps you more easily manage your application's workload needs.
This feature automates read pool scale in and scale out operations based on one or both of the following conditions:
Cloud SQL for PostgreSQL now supports read pool autoscaling (GA), which helps you more easily manage your application's workload needs.
This feature automates read pool scale in and scale out operations based on one or both of the following conditions:
Cloud SQL for MySQL now lets you have more control over the number of results
that are returned when you perform an ANN vector search with filters.
You can use iterative filtering when the selective filters of the
WHERE clause in your ANN search query produce fewer results
than the number of results specified in your LIMIT clause.
To enable iterative filtering for your ANN search query, set the
cloudsql_vector_iterative_filtering flag to ON.
You can set the flag at a session or global level.
To enable and use iterative filtering for your ANN search query, you must have
[MYSQL_$VERSION].R20251004.01_07
or later installed on your MySQL instance.
For more information, see Search approximate nearest neighbors (ANN).
]]>Cloud SQL for MySQL now supports minor version 8.0.44. To upgrade your existing instance to the new version, see Upgrade the database minor version.
]]>Cloud SQL now provides brute-force detection and protection for your Cloud SQL instances. This helps protect your instances from brute-force access attempts by identifying the source and mitigating the risk caused by these attempts. For more information, see Use brute-force protection.
]]>The rollout of the following extension versions, plugin versions, and extension support is underway:
Extensions and plugins
plpgsql_check is upgraded from 2.8.1 to 2.8.3 for PostgreSQL versions
14 and later.pg_wait_sampling is upgraded from 1.1.6 to 1.1.9 for PostgreSQL versions
13 and later.tds_fdw is upgraded from 2.0.4 to 2.0.5.The following extensions are available for PostgreSQL 18:
anonpg_hint_planpg_wait_samplingplpgsql_checktds_fdwTo use these versions of the extensions and plugins, update your instance to
[PostgreSQL version].R20251004.01_14.
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.
]]>Cloud SQL now supports the
automatic minor version upgrade
for Cloud SQL for MySQL 8.0.35 or later instances.
If your Cloud SQL for MySQL instance is running MySQL 8.0.35 or later, but
you didn't select a specific minor version when you created the instance (databaseVersion=MYSQL_8_0),
then your MySQL instance is upgraded automatically to the default minor version
of Cloud SQL for MySQL 8.0 during its regular scheduled maintenance update.
All eligible Cloud SQL for MySQL instances receive the first automatic
minor version upgrade during the rollout of MYSQL_8_0_[N].R20251004.01_07.
You can integrate Cloud SQL for SQL Server with customer-managed Active Directory (CMAD).
CMAD provides capabilities such as authentication and authorization. Joining an instance to a CMAD domain lets you sign in using Windows Authentication with an AD-based identity.
Customer-managed Active Directory (CMAD) is generally available (GA).
]]>Cloud SQL has enhanced the optimized writes feature, which includes an improved crash recovery algorithm to reduce crash recovery time and utilizes unused disk I/O throughput adaptively to accelerate buffer pool warm-up. The optimized writes feature provides a set of write performance improvements that adjust MySQL configurations dynamically based on workload demand and underlying infrastructure.
By default these improvements are enabled for all new Cloud SQL Enterprise Plus edition instances that you create or that you upgrade to from Cloud SQL Enterprise edition.
For more information about optimized writes, see Configure database flags.
]]>The rollout of the following extension versions and plugin versions is underway:
Extensions and plugins
pg_squeeze is upgraded from 1.8 to 1.9 for PostgreSQL version
13 and later.pg_cron is upgraded from 1.6.4 to 1.6.7 for PostgreSQL version
10 and later.postgis is upgraded from 3.5.2 to 3.6.0 for PostgreSQL version
13 and later.rdkit is upgraded from 4.6.1 to 4.7.0.To use these versions of the extensions and plugins, update your instance to
[PostgreSQL version].R20251004.01_07.
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.
]]>Cloud SQL now proactively detects and works to cancel high memory usage connections to prevent out-of-memory (OOM) failures. For more information, see Cancelled queries due to high memory usage.
]]>Cloud SQL Enterprise edition now supports a new machine series called the N4 machine series. This machine series provides balanced price-to-performance and uses the Hyperdisk Balanced storage. You can create custom machine types for the N4 machine series with up to 80 vCPUs and up to 640 GB memory. The N4 machine series is generally available (GA).
For more information about the N4 machine series and its availability, see Machine series overview.
The C4A machine series is now generally available (GA).
The C4A machine series is supported for Cloud SQL Enterprise Plus edition instances, and provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. It uses the Hyperdisk Balanced storage.
For more information about the C4A machine series and its availability, see Machine series overview.
Cloud SQL Enterprise edition now supports a new machine series called the N4 machine series. This machine series provides balanced price-to-performance and uses the Hyperdisk Balanced storage. You can create custom machine types for the N4 machine series with up to 80 vCPUs and up to 640 GB memory. The N4 machine series is generally available (GA).
For more information about the N4 machine series and its availability, see Machine series overview.
The C4A machine series is now generally available (GA).
The C4A machine series is supported for Cloud SQL Enterprise Plus edition instances, and provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. It uses the Hyperdisk Balanced storage.
For more information about the C4A machine series and its availability, see Machine series overview.
Cloud SQL Enterprise edition now supports a new machine series called the N4 machine series. This machine series provides balanced price-to-performance and uses the Hyperdisk Balanced storage. You can create custom machine types for the N4 machine series with up to 80 vCPUs and up to 640 GB memory. The N4 machine series is generally available (GA).
For more information about the N4 machine series and its availability, see Machine series overview.
]]>You can now assess the upgrade readiness of your Cloud SQL for PostgreSQL instances before a major version upgrade by running a precheck. This precheck either confirms your instance can be upgraded, or lists issues and their solutions that need to be fixed prior to upgrading. For more information, see Assess upgrade readiness for your instance.
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:
Cloud SQL for PostgreSQL now supports PostgreSQL version 18 in Preview.
PostgreSQL 18 is a newly supported version. We strongly recommend that you review the changes in the release and validate the readiness of your instance thoroughly prior to upgrading your instance to this version.
The following information applies to flags and extensions for PostgreSQL 18:
Flags
The following new flags are available for PostgreSQL 18 only:
autovacuum_vacuum_max_thresholdautovacuum_worker_slotsenable_distinct_reorderingenable_self_join_elimitationio_max_concurrencyio_methodio_workerslog_lock_failuresmax_active_replecation_originstrack_cost_delay_timingvacuum_max_eager_freeze_failure_ratevacuum_truncateFor more information, see Configure database flags.
Extensions
The following extensions aren't available for PostgreSQL 18:
pgRoutingplpgsql_checkpg_hint_planpgroutinganonymizerpg_wait_samplingtds_fdwFor more information, see Configure PostgreSQL extensions.
To create a new instance using PostgreSQL 18, see Create instances.
]]>You can now use Gemini's capabilities to fix errors in a query within Cloud SQL Studio (Preview).
You can now use Gemini's capabilities to fix errors in a query within Cloud SQL Studio (Preview).
You can now use Gemini's capabilities to fix errors in a query within Cloud SQL Studio (Preview).
]]>Cloud SQL for MySQL now supports minor version 8.0.43. To upgrade your existing instance to the new version, see Upgrade the database minor version.
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. You can now also use IAM authentication to secure connections when using Managed Connection Pooling.
For more information, see Managed Connection Pooling overview.
]]>Cloud SQL for MySQL 8.4.5 is upgraded to MySQL 8.4.6. For more information, see the MySQL 8.4.6 Release Notes.
]]>You can now provision, manage and query your databases using the dedicated Gemini CLI extension for Cloud SQL for MySQL. The extension provides full lifecycle control of your database—from provisioning instances, to exploring schemas and troubleshooting issues—from your command-line interface.
For more information, see Use Cloud SQL for MySQL with MCP, Gemini CLI, and other agents.
You can now retain point-in-time recovery (PITR) logs for an instance after its deletion for a specified retention period. These logs can be used to restore the deleted instance to a specific point in time. For more information, see Restore a deleted instance using PITR.
You can now provision, manage and query your databases using the dedicated Gemini CLI extension for Cloud SQL for PostgreSQL. The extension provides full lifecycle control of your database—from provisioning instances, to exploring schemas and troubleshooting issues—from your command-line interface.
For more information, see Use Cloud SQL for PostgreSQL with MCP, Gemini CLI, and other agents.
You can now retain point-in-time recovery (PITR) logs for an instance after its deletion for a specified retention period. These logs can be used to restore the deleted instance to a specific point in time. For more information, see Restore a deleted instance using PITR.
You can now provision, manage and query your databases using the dedicated Gemini CLI extension for Cloud SQL for SQL Server. The extension provides full lifecycle control of your database—from provisioning instances, to exploring schemas and troubleshooting issues—from your command-line interface.
For more information, see Use Cloud SQL for SQL Server with MCP, Gemini CLI, and other agents.
You can now retain point-in-time recovery (PITR) logs for an instance after its deletion for a specified retention period. These logs can be used to restore the deleted instance to a specific point in time. For more information, see Restore a deleted instance using PITR.
]]>The rollout of the following minor version upgrades is complete:
Minor versions
Cloud SQL for PostgreSQL adds support for the following extensions:
Extensions
plpgsql_check 2.8 is available for PostgreSQL version 14 and later.roaringbitmap 0.5 is available for PostgreSQL version 12 and later.To use these minor versions and the new extensions, update your instance to [PostgreSQL version].R20250727.00_23.
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.
]]>