You can build data agents that interact with the data in yourdatabase using conversational language. Use these data agents as tools toempower your applications. For more information, seeData agents overview. This feature is available inPreview, and access to it requires asign-up.

Cloud SQL enhanced backups are now generally available (GA).

With enhanced backups, backups are managed and stored in a centralizedbackup management project that leverages theBackup and DR service, andprovides enforced retention, granular scheduling, and longer retention.

Enhanced backups now also supportpoint-in-time-recovery (PITR) after instance deletion.

For more information about the available options and their limitations, seeBackup options.For more information about enhanced backups pricing, seeBackup and DR pricing.

PostgreSQL version 18 is nowgenerally availablefor Cloud SQL for PostgreSQL.

You can now useDatabase Migration Servicewith Cloud SQL for PostgreSQL when using PostgreSQL version 18.

To upgrade your instance to PostgreSQL 18, seeUpgrade the database major version in-place.

The following extensions are also now available for PostgreSQL 18:

• pg_hint_plan
• pgrouting
• anonymizer
• pg_wait_sampling
• tds_fdw
• plpgsql_check

For more information about these extensions, seeConfigure PostgreSQL extensions.

The rollout of the following minor version and extension upgrades is complete:

Minor versions

• 13.22 is upgraded to 13.23.
• 14.19 is upgraded to 14.20.
• 15.14 is upgraded to 15.15.
• 16.10 is upgraded to 16.11.
• 17.6 is upgraded to 17.7.
• 18 is upgraded to 18.1.

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, andplugin 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, seeSelf-service maintenance.To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

Cloud SQL for PostgreSQL now supports Vector assist (Preview).

Vector assist is a Cloud SQL for PostgreSQL extension that simplifies thedeployment and management of your Cloud SQL vector workloads. It helps you setup 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,seeVector assist overview.

Cloud SQL now offers a free trial instance for both existing and new GoogleCloud customers. A free trial instance lets you test advanced Cloud SQLcapabilities and features for up to 30 days without any financial commitment.

For information about a free trial instance, and its inclusions and conditions,seeFree trial instance overview.

Cloud SQL for PostgreSQL now supportsread pool autoscaling(GA), which helps youmore easily manage your application's workload needs.

This feature automates read pool scale in and scale out operations based on oneor both of the following conditions:

• Allowed CPU usage of the read pool
• Allowed number of client connections to the read pool

The rollout of the following extension versions, plugin versions, andextension support is underway:

Extensions and plugins

• plpgsql_check is upgraded from 2.8.1 to 2.8.3 for PostgreSQL versions14 and later.
• pg_wait_sampling is upgraded from 1.1.6 to 1.1.9 for PostgreSQL versions13 and later.
• tds_fdw is upgraded from 2.0.4 to 2.0.5.

The following extensions are available for PostgreSQL 18:

• anon
• pg_hint_plan
• pg_wait_sampling
• plpgsql_check
• tds_fdw

To 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, andplugin 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, seeSelf-service maintenance. To findyour maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

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 version13 and later.
• pg_cron is upgraded from 1.6.4 to 1.6.7 for PostgreSQL version10 and later.
• postgis is upgraded from 3.5.2 to 3.6.0 for PostgreSQL version13 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, andplugin 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, seeSelf-service maintenance. To findyour maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

Cloud SQL now proactively detects and works to cancel high memory usageconnections to prevent out-of-memory (OOM) failures. For more information,seeCancelled 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 isgenerally available (GA).

For more information about the N4 machine series and its availability, seeMachine series overview.

TheC4A machine series is nowgenerally 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, seeMachine 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, seeAssess upgrade readiness for your instance.

Cloud SQL for PostgreSQL now supports PostgreSQL version 18 inPreview.

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_threshold
• autovacuum_worker_slots
• enable_distinct_reordering
• enable_self_join_elimitation
• io_max_concurrency
• io_method
• io_workers
• log_lock_failures
• max_active_replecation_origins
• track_cost_delay_timing
• vacuum_max_eager_freeze_failure_rate
• vacuum_truncate

For more information, seeConfigure database flags.

Extensions

The following extensions aren't available for PostgreSQL 18:

• pgRouting
• plpgsql_check
• pg_hint_plan
• pgrouting
• anonymizer
• pg_wait_sampling
• tds_fdw

For more information, seeConfigure PostgreSQL extensions.

To create a new instance using PostgreSQL 18, seeCreate instances.

You can nowuse Gemini's capabilities to fix errors in a query within Cloud SQL Studio (Preview).

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 useIAM authentication to secure connections when using Managed Connection Pooling.

For more information, seeManaged Connection Pooling overview.

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, seeUse 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, seeRestore a deleted instance using PITR.

The rollout of the following minor version upgrades is complete:

Minor versions

• 13.21 is upgraded to 13.22.
• 14.18 is upgraded to 14.19.
• 15.13 is upgraded to 15.14.
• 16.9 is upgraded to 16.10.
• 17.5 is upgraded to 17.6.

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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

If a specific active query is blocked or running much longer than expected, it can block other dependent queries. Cloud SQL for PostgreSQL offers an optional feature that lets you terminate specific long-running or blocked active queries.

For more information, seeBlocked active queries (Preview).

The rollout of the following extension versions is complete:

Extensions and plugins

• pg_ivm is upgraded from 1.9 to 1.11.
• pg_background is upgraded from 1.2 to 1.3.
• google_ml_integration is upgraded from 1.4.2 to 1.4.3.

To use these versions of the extensions, update your instance to [PostgreSQL version].R20250727.00_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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

Cloud SQL read pools are now generally available and provide operational simplicity and scaling for your read workloads.

Read pools provide a single endpoint in front of up to 20 read pool nodes and automatically load balance traffic.

You can scale your read pool in several ways:

• Scale in or out: scale load balancing capacity horizontally by modifying the number of read pool nodes in the read pool. Each read pool supports up to 20 read pool nodes.
• Scale up or down: scale load balancing capacity vertically by modifying the machine type associated with a read pool node. Once defined, configuration is uniformly applied across each read pool node in the read pool.

For more information, seeAbout read pools.

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

This feature is now generally available (GA).

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

PSC outbound connectivity is required forhomogeneous migrations to PSC-enabled Cloud SQL instances usingDatabase Migration Service. For more information, seePSC outbound connections.

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

You can also create acustom organization policy to define final backup instance settings. For more information, seeFinal backup.

You can save and manage SQL queries in Cloud SQL Studio. This feature is inPreview. For more information, seeSaved queries overview.

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

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

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 thenext maintenance window to update your instance automatically. For more information about maintenance, seeMaintenance updates on Cloud SQL instances.

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 forhomogeneous migrations to PSC-enabled Cloud SQL instances usingDatabase Migration Service. For more information, seePSC outbound connections.

Cloud SQL for Enterprise Plus edition supports quality enhancements forAI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues likeslow queries andhigh load for your instances in a guided manner. To use AI-assisted troubleshooting, you needGemini Cloud Assist andquery insights for Enterprise Plus edition.

PostgreSQL has identified abug inPostgreSQL's May 8, 2025 release that is causing logical replication to halt. Cloud SQL for PostgreSQL released[PostgreSQL version].R20250302.00_19 onMay 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 amajor 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, seeLogical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5.

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 theBackup 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, seeBackup options.

The write endpoint feature for Cloud SQL Enterprise Plus edition instances is nowgenerally 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, seeConnect to an instance using a write endpoint.

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, seeConfigure both private services access and Private Service Connect.

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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

You can now useadvanced 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, seeUse advanced disaster recovery (DR). This feature isgenerally available (GA).

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

For users of theCloud SQL Auth Proxy:

• If the Cloud SQL instance to which you're connecting is usingshared certificate authority (CA) for itsserverCaMode 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 usingcustomer-managed CA for itsserverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.

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, seeMigrate from Cloud SQL for PostgreSQL to AlloyDB.

You can nowset 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 thecustomer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.

Custom SAN configuration for instances isgenerally available (GA).

Cloud SQL gives you the flexibility to choose between threeCA hierarchy options when youcreate 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 nowgenerally available (GA).

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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

Private Service Connect endpoint propagation is nowgenerally 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 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 calledHyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available inPreview.

For more information about the C4A machine series and its availability, seeMachine 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, seeUse query insights to improve query performance.

Cloud SQL for Enterprise Plus edition supportsAI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues likeslow queries andhigh load for your instances in a guided manner. To use AI-assisted troubleshooting, you needGemini Cloud Assist andquery insights for Enterprise Plus edition. AI-assisted troubleshooting is available inPreview.

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

Extensions and plugins

• PostGIS is upgraded from 3.4.4 to 3.5.2.

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

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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

Cloud SQL now supports Managed Connection Pooling (MCP) inPreview, which lets you scale your workloads by optimizing resource utilization for your Cloud SQL instances using pooling. To use Managed Connection Pooling, update your instance to[PostgreSQL version].R20250302.00_04.

For more information, seeManaged Connection Pooling overview.

Cloud SQL read pools provide operational simplicity and scaling for your large read workloads.

Read pools provide a single endpoint in front of up to 20 read pool nodes and automatically load balance traffic.

You can scale your read pool in several ways:

• Scale in or out: scale load balancing capacity horizontally by modifying the number of read pool nodes in the read pool. Each read pool supports up to 20 read pool nodes.
• Scale up or down: scale load balancing capacity vertically by modifying the machine type associated with a read pool node. Once defined, configuration is uniformly applied across each read pool node in the read pool.

For more information, seeAbout read pools.

Cloud SQL now lets you retain existing backups after an instance is deleted. These consist of on-demand and automatic backups created when the instance was live. For more information, seeRetained backups.

Cloud SQL Enterprise edition now supports theeurope-north2 (Stockholm) region.

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

Minor versions

• 12.21 is upgraded to 12.22.
• 13.18 is upgraded to 13.20.
• 14.15 is upgraded to 14.17.
• 15.10 is upgraded to 15.12
• 16.6 is upgraded to 16.8.
• 17.2 is upgraded to 17.4.

Extensions and plugins

• PostGIS is upgraded from 3.4.3 to 3.4.4.

To use these versions of the extensions, update your instance to[PostgreSQL version].R20250112.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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

You can now include replicas when you perform an in-place major version upgrade using gcloud or the Cloud SQL Admin API. For more information, seeUpgrade the database major version in-place.

You can nowexport or import all user databases in an instance using a directory-formatted, parallel export or import operation.

You can now create a final backup of your data before you delete a Cloud SQL instance. You can use the final backup to restore your data to a new instance. This way, you can recover your data after you delete the instance. For more information, seeAbout Cloud SQL backups.

Cloud SQL for PostgreSQL now supports thetds_fdw extension. This extension provides a foreign data wrapper (fdw) for accessing databases that use the Tabular Data Stream (TDS) protocol, such as Microsoft SQL Server or Sybase. Cloud SQL for PostgreSQL supportstds_fdw version 2.0.4.For more information about using this extension, seeConfigure PostgreSQL extensions.

You can now performpg_replication_origin_* functions as a database user with thecloudsqlsuperuser role. For more information aboutcloudsqlsuperuser, seeAbout PostgreSQL users and roles.

The rollout of the following extension version is underway:

• rdkit is upgraded from 4.3.0 to 4.6.1

If you use a maintenance window, then the updates to the extension version 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].R20250112.01_03. To learn how to check your maintenance version, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

You can now use a custom DNS name to connect to your Cloud SQL instances by adding a custom subject alternative name (SAN) to your Cloud SQL instances. This feature is available for instances that are configured with Customer Managed CAS CA.. For more information, seeCreate instances.

You can also add, modify, and remove a custom SAN for existing Cloud SQL instances. For more information, seeEdit instances.

This feature is available inPreview.

You can now configure customer-managed CA (CUSTOMER_MANAGED_CAS_CA) as the server certificate authority (CA) mode when you create a Cloud SQL instance. With customer-managed CA mode, you set up your own CA pool and CA inCertificate Authority Service. This option lets you establish your own CA hierarchy and manage the rotation of CA certificates for your Cloud SQL instances to help you meet your regulatory compliance needs.

To use the customer-managed CA option in Cloud SQL, seeUse a customer-managed certificate authority (CA). For more information about server CA mode options, seeCertificate authority (CA) hierarchies. The customer-managed CA feature is inPreview.

You can now migrate a subset of databases from an external server to a destination Cloud SQL instance. For more information, seeConfigure Cloud SQL and the external server for replication.

All Cloud SQL for PostgreSQL 9.6, 10, 11, and 12 instances are running community end-of-life (EOL) major versions and are now enrolled in Cloud SQL extended support.

IMPORTANT: Extended support is a paid service and is an addition to the current cost of your instance. Charges for extended support are waived from February 1, 2025 through April 30, 2025. Starting on May 1, 2025, all instances enrolled in extended support will be charged. To learn more about the benefits of extended support and pricing, seeExtended support for Cloud SQL.

Cloud SQL for PostgreSQL version 17 adds support for the following extensions and plugins:

Extensions and plugins

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

Cloud SQL for PostgreSQL version 17 doesn't support:

• rdkit
• pg_squeeze

To use these extensions and plugins in your PostgreSQL 17 instance, update your instance to thePOSTGRES_17_2.R20241011.00_11 maintenance version.

To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

To start using PostgreSQL 17, seeCreate instances.

You can now migrate data from Microsoft Azure to Cloud SQL. For more information, seeConfigure Cloud SQL and the external server for replication.

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

Minor versions

• 12.20 is upgraded to 12.21. This version restores functionality of theALTER {ROLE|DATABASE} SET role command that's present in PostgreSQL version 12.22. For more information, see thePostgreSQL 12.22 release notes.
• 13.16 is upgraded to 13.18.
• 14.13 is upgraded to 14.15.
• 15.8 is upgraded to 15.10.
• 16.4 is upgraded to 16.6.
• 17.0 is upgraded to 17.2.

Extension and plugin versions

• orafce is upgraded from 4.7 to 4.73 (for PostgreSQL instances, versions 11-16).
• pgAudit is upgraded from 17beta to 17.1 (for PostgreSQL instances, version 17).

To use these versions of the extensions, update your instance to one of the following:

• POSTGRES_17_0.R20241011.00_11 (for PostgreSQL instances, version 17)
• [PostgreSQL version].R20240910.01_31 (for PostgreSQL instances, versions 12 to 16)

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, seeSelf-service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

You can now enable query insights for Cloud SQL Enterprise Plus edition. When you enable query insights for Enterprise Plus, you can access additional features in query insights such as 30 days of metrics retention, granular query plan details, and a higher query length limit.

For more information, seeUse query insights to improve query performance. Query insights for Cloud SQL Cloud SQL Enterprise Plus edition is inPreview.

Cloud SQL now offers notifications for maintenance that's either started or completed. See theOverview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, seeFind and set maintenance windows.

Cloud SQL Enterprise Plus edition now supports the following regions:

• africa-south1 (Johannesburg)
• asia-east2 (Hong Kong)
• europe-west10 (Berlin)

You can now use the Network Connectivity Center hub topropagate Private Service Connect endpoints of Cloud SQL instances in a VPC network. All endpoints in this network become accessible transitively to other spoke VPC networks through the hub. This feature is available inPreview.

You can now create instances with both private services access and Private Service Connect enabled for them. You can also enable Private Service Connect for existing private services access instances. This feature is available inPreview. For more information, seeConfigure both private services access and Private Service Connect.

You can now set up AlloyDB clusters using a copy of your Cloud SQL for PostgreSQL backup. This feature is inPreview. For more information, seeMigrate from Cloud SQL for PostgreSQL to AlloyDB.

You can now authenticate to Cloud SQL Studio by usingIAM database authentication.

For more information about authentication in Cloud SQL Studio, seeManage your data using Cloud SQL Studio.

ForCloud SQL Enterprise Plus edition instances, 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 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. You can use advanced DR on Cloud SQL for PostgreSQL version 12, 13, 14, 15, or 16.

For more information, seeAdvanced disaster recovery (DR) andUse advanced disaster recovery (DR). This feature isgenerally available (GA).

The write endpoint feature is now available inPreview. This endpoint is a global domain name service (DNS) name. This name 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 regional failure. For more information, seeConfigure private IP.

Thepgvector extension is now upgraded from version 0.7.4 to version 0.8.0. Use this extension to store and search for vector embeddings in PostgreSQL databases. For more information, seeConfigure PostgreSQL extensions.

To use this version of the extension, update your instance to one of the following:

• POSTGRES_17_0.R20241011.00_03 (for PostgreSQL instances, version 17)
• [PostgreSQL version].R20240910.01_17 (for PostgreSQL instances, versions 13 to 16)

For more information, seeSelf-service maintenance.

Support for thenorthamerica-south1 (Mexico) region.

Cloud SQL now supports near-zero downtime when you enable or disabledata cache for Cloud SQL Enterprise Plus edition primary instances. For more information, seeAvailability in Cloud SQL.

Cloud SQL now supports near-zero downtime for infrequent scale downs (once every three hours) of the compute size (vCPU, memory) of your Cloud SQL Enterprise Plus edition primary instance.

For more information, seeAvailability in Cloud SQL.

You can now register an AI model endpoint, generate vector embeddings, and invoke predictions by using model endpoint management in Cloud SQL. For more information, seeRegister and call remote AI models in Cloud SQL overview.

You can now create custom organization policies for theBackupRun resource in Cloud SQL instances. In addition, more fields in theInstances resource are available to create custom organization policies. For more information, seeAdd custom organization policies.

You can now have Cloud SQL create a Private Service Connect endpoint automatically instead of creating the endpoint manually after the instance is created. You use this endpoint to access a Cloud SQL instance through a VPC network. For more information, seeConnect to an instance using Private Service Connect. This feature is available inPreview.

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

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

PostgreSQL version 17 is nowgenerally 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 toflags andextensions for PostgreSQL 17:

Flags

These flags are deprecated for PostgreSQL 17:

• old_snapshot_threshold
• trace_recovery_messages

For more information, seeConfigure 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, seeCreate instances.

You can now create a read replica for an instance that hasprivate services access configured for it andconnector enforcement enabled for it. For more information, seeConnect using Cloud SQL Language Connectors.

Thepg_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 thepgRouting extension. This extension extends PostGIS and enhances geospatial processing through network routing and analysis.

For more information on these extensions, seeConfigure PostgreSQL extensions.

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

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, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind 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, seeCertificate authority (CA) hierarchies. This feature is inPreview.

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

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, seeUse point-in-time recovery andSwitch transaction log storage to Cloud Storage.

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, seeAbout 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, seeManage your data using Cloud SQL Studio.

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

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, seeUse point-in-time recovery (PITR).

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, seeClone instances.

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

For more information about extended support, seeExtended support for Cloud SQL.

For more information about extended support timelines, seeDatabase 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, seeUpgrade 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, seeUse point-in-time recovery (PITR).

Gemini in Databases assistance in Cloud SQL for PostgreSQL is now available inPreview 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, seeObserve and troubleshoot with Gemini assistance.

IAM group authentication is now generally available (GA) for Cloud SQL for PostgreSQL. You canadd 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 inPreview.

You can now upgrade the network architecture of a Cloud SQL instance that isn't enabled withhigh-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, seeVerify an instance's high availability configuration.

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

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

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 theDROP <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 theIF EXISTS SQL statement with eachDROP statement that's produced by theclean 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 notexporting files in parallel.

Cloud SQL Studio is nowgenerally available. For more information, seeManage your data using Cloud SQL Studio.

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

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

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

You can now use thegcloud 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, seePlan a major version upgrade.

Thetemporal_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, seeConfigure PostgreSQL extensions.

You can now performCREATE CAST andDROP CAST statements as a database user with thecloudsqlsuperuser role. For more information, seeAbout PostgreSQL users and roles.

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

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

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].R20240514.00_04. To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind 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 namedWeek 5.

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

• Order of update is renamed toMaintenance timing
• Earlier is renamed toWeek 1
• Later is renamed toWeek 2

For more information, seeMaintenance settings andFind and set maintenance windows.

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, seeCreate instances.

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, seeExtended support for Cloud SQL.

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

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, seeUse Query Insights to improve query performance.

Thepgvector 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, seeConfigure PostgreSQL extensions.

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

The followingGemini 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 theQuery Insights dashboard.
• 15 new database insight recommendations.

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

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

You can nowmigrate 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 tomin,optimal, ormax.

Version 0.6.0 of thepgvector extension that's listed in theMarch 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 aCloud SQL Enterprise Plus edition primary instance with near-zero downtime.

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

The rollout of the following items in theFebruary 7 release note is nowcomplete:

• Extensions
• Flags
• Minor versions
• Extension versions
• Plugin versions

Thepgvector 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, seeConfigure PostgreSQL extensions.

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

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, seeIntegrate Cloud SQL with Vertex AI.

Private Service Connect now includes support forcross-region read replicas. You can alsochoose an availability type (REGIONAL or ZONAL) for Private Service Connect-enabled instances. Both features are inGA.

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

You can now upgrade network architecture for your HA-enabled instances in a region, even if you have multiple instances in your network and region. For more information, seeUpgrade an instance to the new network architecture.

The new maintenance version listed in theFebruary 7th entry for PostgreSQL extensions, flags, minor versions, extension versions, and plugin versions is[PostgreSQL version].R20240130.00_05.

Cloud SQL Enterprise Plus edition now supports versions 12 and 13 of PostgreSQL. For more information, seeIntroduction to Cloud SQL editions.

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

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

The rollout of the following extensions and flags isunderway:

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 thepg_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 isunderway:

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.

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].R20240130.00_00. To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

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

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

Support forafrica-south1 (Johannesburg) region.

You can now use thepg_dump andpg_restore utilities to export and import data for multiple files in parallel. For more information, seeExport and import files in parallel.

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 Enterprise Plus edition now supports the following regions:

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

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

The followingflags are generally available:

• autovacuum_vacuum_insert_scale_factor: specify a fraction of the size of a database table to add to theautovacuum_vacuum_insert_threshold flag. Use this flag when you're deciding whether to run aVACUUM.
• autovacuum_vacuum_insert_threshold: specify the minimum number of inserted records or rows (tuples) that you need to run aVACUUM 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'spg_class.relfrozenxid field can attain before aVACUUM 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'spg_class.relminmxid field can attain before aVACUUM takes extraordinary measures to avoid a system-wide wraparound failure for multiple transaction IDs.

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

You can now upgrade your Cloud SQL instances to use the new network architecture to get additional capabilities not available in the old network architecture. For more information, seeUpgrade an instance to the new network architecture.

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

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, seeUpgrade an instance by using in-place upgrade.

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

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

The rollout of the following items iscomplete:

• Theoracle_fdw extension, version 1.2
• The minor versions, extension versions, and plugin versions listed in theSeptember 21 release note

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, seeEnforce SSL/TLS encryption.

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

The following pg_wait_sampling and rdkitflags are generally available:

pg_wait_sampling flags

• cloudsql.enable_pg_wait_sampling: enable thepg_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.

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, seeImprove instance reliability by enabling high availability.

The rollout of theoracle_fdw extension, version 1.2 isunderway. This extension provides a foreign data wrapper for accessing Oracle databases easily and efficiently. For more information, seeConfigure PostgreSQL extensions.

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

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.

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].R20230830.01_00. To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

Support forme-central2 (Dammam) region.

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

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

Support foreurope-west10 (Berlin) region.

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.

Cloud SQL Enterprise Plus edition now supports four new regions:

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

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

Cloud SQL Enterprise Plus edition now supports the asia-northeast3 (Seoul) region.

You can now use point-in-time recovery torecover a Cloud SQL instance that isn't available. If the instance is unavailable, then you can use the API toget the latest recovery time and perform the recovery of the instance to that time.

You can now upgrade a Cloud SQL for PostgreSQL instance to Cloud SQL Enterprise Plus edition by usingIP allowlists andVPC Peering.

Cloud SQL now supports multiple categories of API rate quotas. Rate quotas for each category are imposed per minute, per project, per region, and per user. For more information about rate quotas for each category, seeQuotas and limits.

TheCloud SQL Node.js Language Connector is now available for public preview.

Cloud SQL now supportsdefault maintenance windows for your instances. With this release, an instance without a user-specified maintenance window is maintained outside of the typical business hours for the time zone that the instance is deployed in.

You can nowenable query insights for multiple instances at a time.

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

Cloud SQL Editions are only available for Cloud SQL for MySQL and Cloud SQL for PostgreSQL.

For more information about Cloud SQL editions, seeIntroduction to Cloud SQL editions.

Cloud SQL now supportscancelling the import and export of data into Cloud SQL for PostgreSQL instances.

Cloud SQL now supportsnon-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.

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.

TheCloud SQL System insights dashboard is now generally available and includes moremetrics. You can also use theCustomize dashboard option to personalize the dashboard and choose the metrics you want to see on it.

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)

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].R20230530.01_00. To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

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

The followingextensions,views,utilities, andflags 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

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

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.

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

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, seeExternal Server Cascading Replicas.

Support forme-central1 (Doha) region.

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.

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].R20230316.02_02. To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

The changes in the September 15, 2022 Release Notes entry for read replica maintenance are now available. Cloud SQL read replicas follow themaintenance 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, seeHow does maintenance affect read replicas?

Support foreurope-west12 (Turin) region.

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.

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, seeCloud SQL Admin API REST Resource.

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, seeAbout the Cloud SQL Proxy Operator.

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 withCloud Monitoring andCloud Trace
• Support forPrometheus
• Service account impersonation
• Separate Dialer functionality released as theCloud SQL Go Connector
• Configuration with environment variables
• Fully POSIX-compliant flags

We recommend all customers upgrade to v2 and have released amigration guide. For more information, seeCloud SQL Auth proxy.

Cloud SQL supports the preview version of theUnderprovisioned 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 now supportsviewing 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.

For new Cloud SQL instances that havepoint-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.

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, seeCreate instances.

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

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

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

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:

1. TheC.UTF-8 collation is renamed toC.utf8. The original name is supported as an alias of the new name.

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

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].R20221017.01_00. To learn how to check your maintenance version, seeSelf service maintenance. To find your maintenance window or to manage maintenance updates, seeFind and set maintenance windows.

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

Cloud SQL for PostgreSQL now supports thelog_timezone andTimeZone flags. For more information, see theConfigure database flags page.

Terraform is supported when you useself-service maintenance.

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

Cloud SQL allows the re-use of an instance name immediately after the instance is deleted. For more information, see theCloud SQL for PostgreSQL FAQ.

Cloud SQL read replicas now follow themaintenance 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, seeHow does maintenance affect read replicas?

Support for me-west1 (Tel Aviv).

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.

The following extensions in Cloud SQL for PostgreSQL aregenerally 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.

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

For more information, seePrevent deletion of an instance.

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

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 youcheck your current maintenance version, you can apply a fix by performing aself-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:

After you have identified the name of the maintenance version, pleaseupgrade 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.

Added information about checking theLC_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 theCloud SQL documentation.

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, seeFind and set maintenance windows.

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

You can createexternal server replicas with HA enabled.

The July maintenance changelog is now available. For more information, use the links atMaintenance changelog.

A second June maintenance changelog is now available. For more information, use the links atMaintenance changelog.

The fix to the silent data corruption when using the CREATE INDEX CONCURRENTLY or REINDEX CONCURRENTLY SQL commands in PostgreSQL 14 (BUG #17485) is now available in the self-service maintenance release POSTGRES_14_2.R20220331.02_012 for PostgreSQL 14.2.

After applying theself service maintenance, you can fix any silent data corruption if it already happens using REINDEX CONCURRENTLY SQL command on the specific indexes, or reindexdb client command for your entire instance.

Cloud SQL for PostgreSQL now supportsreplication from an external server.

For enhanced security with built-in authentication, Cloud SQL now lets you setpassword policies at the instance level.

The following extensions in Cloud SQL for PostgreSQL aregenerally available:

• pg_bigm. Enables full text search and allows a two-gram (bigram) index for faster full text search.
• refint. Enables the checking of foreign key restraints, the referencing table, and the referenced table.
• decoderbufs. A logical decoder that delivers output data as Protocol Buffers, adapted for Debezium.
• pg_wait_sample. Collects sampling statistics of wait events, providing wait event data for processes on servers.

Additionally, users with thecloudsqlsuperuser role have full access to thepg_largeobject system catalog.

Cloud SQL enables you to access to thepg_shadow view. You can use thepg_shadow view to work with the properties of roles that are marked asrolcanlogin in thepg_authid catalog.

For more information, seeAccess to the pg_shadow view.

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

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

New maintenance versions are now available throughself-service maintenance. See themaintenance 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 atMaintenance changelog.

Support for us-south1 (Dallas).

Support for us-east5 (Columbus).

Support for europe-west9 (Paris).

New maintenance versions are now available throughself-service maintenance. See themaintenance changelog to learn more about these new maintenance versions.

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 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, seeCloud SQL maintenance changelogs.

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 useself-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, seeFinding 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.

Support for europe-west8 region (Milan).

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

• 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, seeCustomer-managed encryption keys (CMEK) organization policies. To add CMEK organization policies now, seeAdd Cloud SQL organization policies.

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, seeUpgrade the database major version in-place.

Due to a change in a recent maintenance update, the changes listed in theFebruary 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 theInstance Overview page, review the instance'soperations and logs for an occurrence of a maintenance operation since January 27.

If your primary instance uses a private IP address, you can now select an allocated IP range forclones andreplicas created from the instance.

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, seeAccess control with Google Cloud tags. To use tags now, seeAttach and manage tags on Cloud SQL instances.

Cloud SQL supports themax_parallel_maintenance_workers,max_parallel_workers,
max_parallel_workers_per_gather, andmax_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, seeSupported flags.

Cloud SQL supports thewal_receiver_timeout andwal_sender_timeout flags:

• Thewal_receiver_timeout flag ends replication connections that are inactive for the specified time.
• Thewal_sender_timeout flag, which is for detection by the ending server, ends replication connections that are inactive for the specified time.

For more information, seeSupported flags.

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, seeFinding and setting maintenance windows.

• 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, seePostgreSQL 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.

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

The Key Access Justifications (KAJ) feature is now generally available in Cloud SQL. You can use KAJ as part ofCloud 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 theOverview.

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

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

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

The following extensions in Cloud SQL for PostgreSQL aregenerally 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 theEXPLAIN 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 usepg_top with Cloud SQL for PostgreSQL, and generate reports from the operating system process table.

Support forsouthamerica-west1 (Santiago) region.

• 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, seeFinding 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.

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, seeSupported flags.

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, seeOverview of Access Approval. To set up access approval now, see theAccess Approval Quickstart.

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, seeStopping an instance.

Cloud SQL for PostgreSQL has enhanced the support for multiline log entries inpostgres.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, seeour documentation.

The Cloud SQLout-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 now supports themin_wal_size flag. For more information about this flag, see theCloud SQL for PostgreSQL flags documentation.

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

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 now supports the following flags:

• huge_pages
• shared_buffers
• wal_buffers

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

Cloud SQL now supportsIAM Conditions.

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

Cloud SQL now offersfaster maintenance, with connectivity dropping for less than 30 seconds on average.

The Cloud SQL Admin API v1 is now generally available. It isand will continue to be compatible with the v1beta4 version. There is norequirement to migrate from v1beta4 to the v1 Admin API.

Support fornorthamerica-northeast2-a,b,c (Toronto) region.

• 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 theCloud SQL for PostgreSQL flags documentation.

• 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, seeFinding 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.

Support forasia-south2 (Delhi) region.

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

Support foraustralia-southeast2 (Melbourne) region.

Query Insights is now supported for read replicas.

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

Both theCloud SQL Java Connector andCloud SQL Python Connector now support IAM Authentication 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, seeSetting up logical replication and decoding.

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

Also, the default value for the database flagautovacuum_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:

Cloud SQL supports the preview version of theout-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.

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, seeFinding 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 seethe PostgreSQL release notes.

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, seeUsing IAM database authentication with the Cloud SQL Auth proxy.

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

Support foreurope-central2 (Warsaw ).

The following extensions in Cloud SQL for PostgreSQL aregenerally 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.

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

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, seeFinding and setting maintenance windows.

• PostgreSQL 9.6.19 is upgraded to 9.6.20.
• PostgreSQL 10.14 is upgraded to 10.15.
• PostgreSQL 11.9 is upgraded to 11.10.
• PostgreSQL 12.4 is upgraded to 12.5.
• PostgreSQL 13 is upgraded to 13.1.

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, seeUsing the Cloud SQL Admin API.

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, seeImproving query performance.

Database auditing in Cloud SQL for PostgreSQL isgenerally available, through the open-source pgAudit extension. Using this extension, you can selectively record and track SQL operations performed against a given database instance.

The pgAudit extension helps you configure many of the logs often required to comply with government, financial, and ISO certifications.

Cloud SQL now exposes the metricdatabase/memory/total_usage. This metric provides visibility into the database working set (including buffer cache). You can find this metric in theMetrics explorer within the Monitoring dashboard.

For more information aboutdatabase/memory/total_usage, seeCloud SQL Metrics.

IAM database authentication for Cloud SQL for PostgreSQL is now generally available. To get started using IAM database authentication, see theOverview of Cloud SQL IAM database authentication.

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.

Cloud SQL has expanded support for PostgreSQL extensions. Three additional PostgreSQL extensions are now available:

• dblink
• ip4r
• prefix

For additional information, seePostgreSQL extensions.

Cloud SQL for PostgreSQL now supports the effective_cache_size flag.

Cloud SQL for PostgreSQL now supportsretention 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 supportsretention 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.

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

Cloud SQL for PostgreSQL now offers IAM database authentication to help youbetter 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 theOverview of Cloud SQL IAM database authentication. To configure an instance, seeConfiguring instances for IAM database authentication. To create users or service accounts, seeCreating and managing users that use IAM database authentication.

Database auditing in Cloud SQL for PostgreSQL isavailable through the open-source pgAudit extension. Using this extension, you can selectively record and track SQL operations performed against a given database instance.

The pgAudit extension helps you configure many of the logs often required to comply with government, financial, and ISO certifications.

Cloud SQL now offers "deny maintenance periods". Withdeny 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 now offers serverless export. Withserverless export, Cloud SQL performs the export from a temporary instance. Offloading the export operation allows databases on the primary instance to continue to serve queries and perform other operations at the usual performance rate.

The following PostgreSQL minor versions have been upgraded:

• PostgreSQL 9.6.16 is upgraded to 9.6.18.
• PostgreSQL 10.11 is upgraded to 10.13.
• PostgreSQL 11.6 is upgraded to 11.8.
• PostgreSQL 12.1 is upgraded to 12.3.

Cloud SQL now supportspoint-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.

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 thedocumentation for more details.

Support forasia-southeast2 region (Jakarta).

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

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.

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

For information about these newly-added extensions, seePostgreSQL extensions.

Support forus-west4 region (Las Vegas).

PostgreSQL version 12 is now Beta. To start using PostgreSQL 12, seeCreating instances.

PostgreSQL version 10 is now generally available. To start using PostgreSQL 10, seeCreating instances.

Cloud SQL now supports 96-core machine types for MySQL, Postgres, and SQL Server instances. For pricing-related information, see thePricing page.

Cloud SQL now supports read replicas in a different region than that of the primary instance, providing additional protection against regional outages and improving read performance by making replicas available closer to your application. To get started, seeCross-region replicas.

Cloud SQL instances usingprivate IP are now accessible across regions, at the regular cross-region network egress cost.

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

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

Support forasia-northeast3 region (Seoul).

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, seeConfiguring VPC Service Controls.

You can now use Cloud VPN with Cloud SQL. To get started, seeUsing 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, seeConnection organization policies. To use this feature, seeSetting organization policies for Cloud SQL.

Cloud SQL now offers notifications for upcoming maintenance. See theOverview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, seeFinding and setting maintenance windows.

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 theOverview of Access Transparency.

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 theOverview of customer managed encryption keys (CMEK). To start using CMEK, seeUsing customer-managed encryption keys (CMEK).

PostgreSQL version 11 is now generally available. PostgreSQL 11 is the default version when creating new instances. To start using PostgreSQL 11, seeCreating Instances.

This release increases the maximum data storage for instances of MySQL (MySQL Second Generation) and PostgreSQL. The maximum data storage is increased from 10,230 GB to 30,720 GB. For Cloud SQL storage limits, seeLimits. You can limit your automatic storage increases; seeAutomatic storage increase limit.

Cloud SQL now allows you to specify a location for backups, and to restrict data to a single region. To learn about custom backup locations, seeCustom backup locations. To learn how to set a custom location for a backup, seeSetting and viewing a custom location for backups.

Support forasia-northeast2 region (Osaka, Japan).

Cloud SQL now supports PostgreSQL version 11.1 Beta. To start using PostgreSQL 11 Beta, seeCreating Instances.

Support added for 122 MySQL flags and 96 PostgreSQL flags. SeeSupported PostgreSQL Flags andSupported MySQL Flags.

Support foreurope-west6 region (Zürich, Switzerland).

Cloud SQL for PostgreSQL connection limits are now double when memory is 6 GiB or higher. Seethe connection limits table for details.

GA support forPrivate IP connectivity.

Support for CSV format for PostgreSQL instanceimports andexports.

Support forasia-east2 region (Hong Kong).

Proxy version 1.12 released.

Beta support forprivate IP (private services access) connectivity.

PostGIS extension includes full support for JSON-C.

Support forus-west2 region (Los Angeles).

Support foreurope-north1 region (Finland).

Support forrotating SSL certificates.

Support for connecting fromCloud Functions^Beta.

Support forasia-southeast1 region (Singapore).

GA support forCloud SQL for PostgreSQL.

Support foreurope-west4 region (Netherlands).

Maximum concurrent connections to App Engine updated from 12 to 60.

MySQL 5.6 minor version upgraded to 5.6.36.

Support fornorthamerica-northeast1 region (Montréal).

Connection limits for PostgreSQL instances changed.Learn more.

Beta support forthe high availability configuration andreplication for PostgreSQL instances.

Proxy version 1.11 released.

Support forasia-south1 region (Mumbai).

Support forsouthamerica-east1 region (São Paulo).

Support for 64-coremachine types for MySQL instances and 64 cores for PostgreSQL instances.

Support foreurope-west3 region (Frankfurt).

Support foreurope-west2 region (London).

Proxy version 1.10 released.

Support forlabels.

Support foraustralia-southeast1 region (Sydney).

Support for the following PostgreSQLextensions: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.

Support for theJDBC Socket Library for PostgreSQL.

Support forus-east4 region (Northern Virginia).

Support forus-west1 region (Oregon).

GA support for Second Generation and PostgreSQL instances in version 157.0.0 of thegcloud command-line tool. Thebeta version is no longer required for these instances.

Proxy version 1.09 released.

Cloud SQL for PostgreSQL Beta availability.

To provide feedback on the beta release, go toour Cloud SQL user forum.