<?xml version="1.0" encoding="UTF-8"?>
<!-- AUTOGENERATED FILE. DO NOT EDIT. -->
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>tag:google.com,2016:cloud-sql-release-notes</id>
  <title>Cloud SQL - Release notes</title>
  <link rel="self" href="https://docs.cloud.google.com/feeds/cloud-sql-release-notes.xml"/>
  <author>
    <name>Google Cloud Platform</name>
  </author>
  <updated>2026-11-16T00:00:00-08:00</updated>

  <entry>
    <title>November 16, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#November_16_2026</id>
    <updated>2026-11-16T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#November_16_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>When you enable the <a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
integration on an eligible Cloud SQL for MySQL instance created before April 18,
2026 where the integration is currently turned off, the instance now syncs schema
and metadata updates to Knowledge Catalog in near real-time instead of once a day.
Instances created on or after April 18, 2026 have near real-time sync enabled by
default.</p>
<p>This feature is available for instances running MySQL version 8.0 or later on the
<a href="https://docs.cloud.google.com/sql/docs/mysql/upgrade-cloud-sql-instance-new-network-architecture#overview">new network architecture</a>.
If Knowledge Catalog integration is already enabled on the instance with
once a day updates, you can <a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration#deactivate-dataplex-catalog">deactivate</a>
and re-enable the integration to switch to near real-time updates.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration#enable-dataplex-catalog">Enable the integration of Knowledge Catalog on an existing Cloud SQL instance</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>When you enable the <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
integration on an eligible Cloud SQL for PostgreSQL instance created before
April 18, 2026 where the integration is currently turned off, the instance now
syncs schema and metadata updates to Knowledge Catalog in near real-time instead
of once a day. Instances created on or after April 18, 2026 have near real-time
sync enabled by default.</p>
<p>This feature is available for instances running PostgreSQL version 14.0 or later
on the <a href="https://docs.cloud.google.com/sql/docs/postgres/upgrade-cloud-sql-instance-new-network-architecture#overview">new network architecture</a>.
If Knowledge Catalog integration is already enabled on the instance with
once a day updates, you can <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration#deactivate-dataplex-catalog">deactivate</a>
and re-enable the integration to switch to near real-time updates.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration#enable-dataplex-catalog">Enable the integration of Knowledge Catalog on an existing Cloud SQL instance</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>November 13, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#November_13_2026</id>
    <updated>2026-11-13T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#November_13_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>Cloud SQL enhanced backups support instances with disaster recovery (DR)
replica instances. You can associate a Backup and DR backup plan directly with a
primary instance that has a designated DR replica.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/backup-recovery/backup-options#eb-dr-replicas">Choose your backup
option</a> and
<a href="https://docs.cloud.google.com/sql/docs/mysql/backup-recovery/manage-enhanced-backups">Manage enhanced
backups</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>Cloud SQL enhanced backups support instances with disaster recovery (DR)
replica instances. You can associate a Backup and DR backup plan directly with a
primary instance that has a designated DR replica.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/backup-recovery/backup-options#eb-dr-replicas">Choose your backup
option</a> and
<a href="https://docs.cloud.google.com/sql/docs/postgres/backup-recovery/manage-enhanced-backups">Manage enhanced
backups</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>Cloud SQL enhanced backups support instances with disaster recovery (DR)
replica instances. You can associate a Backup and DR backup plan directly with a
primary instance that has a designated DR replica.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/backup-options#eb-dr-replicas">Choose your backup
option</a> and
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/manage-enhanced-backups">Manage enhanced
backups</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>November 09, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#November_09_2026</id>
    <updated>2026-11-09T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#November_09_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/mysql/machine-series-overview#c4d">C4D machine series</a> is
available for Cloud SQL for MySQL Enterprise Plus instances in the following
regions:</p>
<ul>
<li><code>africa-south1</code> — Johannesburg</li>
<li><code>asia-northeast1</code> — Tokyo</li>
<li><code>europe-west1</code> — Belgium</li>
<li><code>europe-west2</code> — London</li>
<li><code>europe-west3</code> — Frankfurt</li>
<li><code>europe-west4</code> — Netherlands</li>
<li><code>europe-west9</code> — Paris</li>
<li><code>us-east1</code> — South Carolina</li>
<li><code>us-east4</code> — Northern Virginia</li>
</ul>
<p>The C4D machine series provides the following benefits:</p>
<ul>
<li>Runs on 5th Generation AMD EPYC processors (Turin) and Google Titanium.</li>
<li>Uses Hyperdisk Balanced storage with customizable IOPS and throughput.</li>
<li>Delivers consistent, predictable high performance for demanding workloads.</li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/postgres/machine-series-overview#c4d">C4D machine series</a> is
available for Cloud SQL for PostgreSQL Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>africa-south1</code> — Johannesburg</li>
<li><code>asia-northeast1</code> — Tokyo</li>
<li><code>europe-west1</code> — Belgium</li>
<li><code>europe-west2</code> — London</li>
<li><code>europe-west3</code> — Frankfurt</li>
<li><code>europe-west4</code> — Netherlands</li>
<li><code>europe-west9</code> — Paris</li>
<li><code>us-east1</code> — South Carolina</li>
<li><code>us-east4</code> — Northern Virginia</li>
</ul>
<p>The C4D machine series provides the following benefits:</p>
<ul>
<li>Runs on 5th Generation AMD EPYC processors (Turin) and Google Titanium.</li>
<li>Uses Hyperdisk Balanced storage with customizable IOPS and throughput.</li>
<li>Delivers consistent, predictable high performance for demanding workloads.</li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>Starting November 9, 2026, newly created Cloud SQL for SQL Server instances
send metadata and schema updates to
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
in <a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration#near-real-time">near real-time</a>.</p>
<p>Integration with Knowledge Catalog is enabled by default for newly created
instances. You can <a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration#verify-dataplex-catalog">verify</a>
or <a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration#deactivate-dataplex-catalog">update the integration</a>
at any time.</p>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview#c4d">C4D machine series</a> is
available for Cloud SQL for SQL Server Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>africa-south1</code> — Johannesburg</li>
<li><code>asia-northeast1</code> — Tokyo</li>
<li><code>europe-west1</code> — Belgium</li>
<li><code>europe-west2</code> — London</li>
<li><code>europe-west3</code> — Frankfurt</li>
<li><code>europe-west4</code> — Netherlands</li>
<li><code>europe-west9</code> — Paris</li>
<li><code>us-east1</code> — South Carolina</li>
<li><code>us-east4</code> — Northern Virginia</li>
</ul>
<p>The C4D machine series provides the following benefits:</p>
<ul>
<li>Runs on 5th Generation AMD EPYC processors (Turin) and Google Titanium.</li>
<li>Uses Hyperdisk Balanced storage with customizable IOPS and throughput.</li>
<li>Delivers consistent, predictable high performance for demanding workloads.</li>
</ul>
]]>
    </content>
  </entry>

  <entry>
    <title>November 04, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#November_04_2026</id>
    <updated>2026-11-04T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#November_04_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>Cloud SQL for SQL Server now supports <a href="https://docs.cloud.google.com/sql/docs/sqlserver/read-pool-autoscaling">read pool autoscaling</a>
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>),
which helps you more easily manage your application's workload needs.</p>
<p>This feature automates read pool scale in and scale out operations based on one
or both of the following conditions:</p>
<ul>
<li>Allowed CPU usage of the read pool</li>
<li>Allowed number of client connections to the read pool</li>
</ul>
<h3>Change</h3>
<p>Cloud SQL for SQL Server supports
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/use-system-insights">additional metrics within the system insights dashboard</a>
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>) related to
engine memory, performance, and replication.</p>
<p>For a detailed list of metrics and their descriptions, see <a href="https://docs.cloud.google.com/sql/docs/sqlserver/use-system-insights#default-metrics">Cloud SQL for SQL Server default metrics</a> and <a href="https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/metrics">Cloud SQL metrics</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>November 03, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#November_03_2026</id>
    <updated>2026-11-03T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#November_03_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>The rollout of the following Cloud SQL for PostgreSQL minor version and
extension upgrades is complete:</p>
<p><strong>Minor versions</strong></p>
<ul>
<li><p>14.23 is upgraded to 14.24.</p></li>
<li><p>15.18 is upgraded to 15.19.</p></li>
<li><p>16.14 is upgraded to 16.15.</p></li>
<li><p>17.10 is upgraded to 17.11.</p></li>
<li><p>18.4 is upgraded to 18.6. This version includes a backported fix for
<a href="https://git.postgresql.org/gitweb/?p=postgresql.git;h=caa463e3f8d2b9c1441e6a59c50f90b8598439f3">PostgreSQL bug #19616</a>
that prevents logical decoding from emitting <code>STREAM_ABORT</code> messages for
unstreamed transactions when an aborted transaction with a subtransaction is
truncated during memory eviction.</p></li>
</ul>
<p><strong>Extensions</strong></p>
<ul>
<li><p><code>hll</code> (<code>postgresql-hll</code>) is upgraded from 2.18 to 2.20.</p></li>
<li><p><code>pg_qualstats</code> is upgraded from 2.1.2 to 2.1.4.</p></li>
<li><p><code>pglogical</code> is upgraded from 2.4.5 (for PostgreSQL 17 and earlier) and 2.4.6
(for PostgreSQL 18) to 2.4.8.</p></li>
<li><p><code>pgTAP</code> is upgraded from 1.3.0 to 1.3.4.</p></li>
<li><p><code>pgtt</code> is upgraded from 4.0 to 4.6.0 for PostgreSQL 12 and later.</p></li>
<li><p><code>PL/Proxy</code> is upgraded from 2.11.0 to 2.12.0.</p></li>
<li><p><code>PostGIS</code> is upgraded from 3.5.2 (for PostgreSQL 13 through 17) and 3.6.0
(for PostgreSQL 18) to 3.6.4 for PostgreSQL 13 and later.</p></li>
<li><p><code>roaringbitmap</code> (<code>pg_roaringbitmap</code>) is upgraded from 0.5 to 1.2 for
PostgreSQL 12 and later.</p></li>
</ul>
<p>The new maintenance version is
<a href="https://docs.cloud.google.com/sql/docs/postgres/maintenance-changelog"><code>[PostgreSQL version].R20261013.02_04</code></a>.
If you use a maintenance window, then the updates to the minor and extension
versions happen according to the timeframe that you set in the window.
Otherwise, the updates occur within the next few weeks.</p>
<p>For more information about checking your maintenance version, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/self-service-maintenance">Perform self-service maintenance</a>.
To find your maintenance window or to manage maintenance updates, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/set-maintenance-window">Find and set maintenance windows</a>.
For more information about supported extensions, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/extensions">Configure PostgreSQL extensions</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 30, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_30_2026</id>
    <updated>2026-10-30T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_30_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Announcement</h3>
<p>Starting November 1, 2026, at 02:00 a.m. local time, unpatched Cloud SQL for MySQL
instances that evaluate certain local Canadian time zones (across Alberta,
British Columbia, Manitoba, and Northwest Territories) will lag by one hour
because the instances still follow the autumn fall back schedule.
Stored timestamp data isn't modified.</p>
<p><strong>What should I do?</strong></p>
<p>Before November 1, 2026, do one of the following fixes:</p>
<ul>
<li><p><strong>Apply self-service maintenance (Recommended):</strong> If your applications rely
on database functions to calculate, schedule, or display times in these
Canadian time zones (such as Calgary, Edmonton, Vancouver, or Winnipeg),
then update your instances to the latest maintenance release using the
Google Cloud console or the gcloud CLI.</p>
<p>Updated time zone rules that reflect permanent standard daylight offsets across
Alberta, British Columbia, Manitoba, and Northwest Territories are supported
in Cloud SQL for MySQL <a href="https://docs.cloud.google.com/sql/docs/mysql/maintenance-changelog">maintenance release <code>*.R20260726.00_36</code> or later</a>.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/self-service-maintenance">Perform self-service maintenance</a>.</p></li>
<li><p><strong>Database configuration stopgap:</strong> If your organization can't
restart instances before November 1, 2026, then you can set the time zone
for your database session without causing downtime for your instance. Set
the <code>default_time_zone</code> flag for the database session to your target fixed
numeric offset (for example, <code>'-06:00'</code> for Alberta, <code>'-07:00'</code> for British
Columbia, or <code>'-05:00'</code> for Manitoba).</p>
<p>For more information about configuring database flags, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/flags">Configure database flags</a>.</p></li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Announcement</h3>
<p>Starting November 1, 2026, at 02:00 a.m. local time, unpatched Cloud SQL for PostgreSQL
instances that evaluate certain local Canadian time zones (across Alberta,
British Columbia, Manitoba, and Northwest Territories) will lag by one hour
because the instances still follow the autumn fall back schedule.
Stored timestamp data isn't modified.</p>
<p><strong>What should I do?</strong></p>
<p>Before November 1, 2026, do one of the following fixes:</p>
<ul>
<li><p><strong>Apply self-service maintenance (Recommended):</strong> If your applications rely
on database functions to calculate, schedule, or display times in these
Canadian time zones (such as Calgary, Edmonton, Vancouver, or Winnipeg),
then update your instances to the latest maintenance release using the
Google Cloud console or the gcloud CLI.</p>
<p>Updated time zone rules that reflect permanent standard daylight offsets across
Alberta, British Columbia, Manitoba, and Northwest Territories are supported
in Cloud SQL for PostgreSQL <a href="https://docs.cloud.google.com/sql/docs/postgres/maintenance-changelog">maintenance release <code>*.R20260712.01_44</code> or later</a>.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/self-service-maintenance">Perform self-service maintenance</a>.</p></li>
<li><p><strong>Database configuration stopgap:</strong> If your organization can't
restart instances before November 1, 2026, then you can set your database
session time zone without downtime to an anchor zone.</p>
<pre class="prettyprint lang-sh">
ALTER DATABASE <var>database_name</var> SET timezone TO '<var>anchor_zone</var>';
</pre>
<p>Replace the following:</p>
<ul>
<li><code><var>database_name</var></code>: the name of your database.</li>
<li><p><code><var>anchor_zone</var></code>: the anchor zone to use as the time zone
for your database. Specify an anchor zone that operates on a permanent
offset.</p>
<p>For example, <code>'America/Regina'</code> for Alberta and Northwest Territories
(UTC-6), <code>'America/Whitehorse'</code> for British Columbia (UTC-7), or
<code>'America/Coral_Harbour'</code> for Manitoba (UTC-5).</p></li>
</ul></li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Announcement</h3>
<p>Starting November 1, 2026, at 02:00 a.m. local time, Cloud SQL for SQL Server
instances that evaluate certain local Canadian time zones (across Alberta,
British Columbia, Manitoba, and Northwest Territories) will lag by one hour
because the instances still follow the autumn fall back schedule.
Stored timestamp data isn't modified.</p>
<p><strong>What should I do?</strong></p>
<p>For SQL Server, Microsoft has
<a href="https://devblogs.microsoft.com/azure-sql/canadas-2026-time-zone-updates-guidance-for-microsoft-sql/">published guidance</a>,
recommending updating each applicable instance's time zone to the Windows time
zone with the matching fixed offset.</p>
<p>Update each instance's time zone to the Windows time zone with the matching
fixed offset:</p>
<table>
<thead>
<tr>
<th>Jurisdiction</th>
<th>Current time zone</th>
<th>Recommended time zone</th>
<th>Fixed offset</th>
</tr>
</thead>
<tbody>
<tr>
<td>British Columbia</td>
<td>Pacific Standard Time</td>
<td>Yukon Standard Time</td>
<td>UTC-07:00</td>
</tr>
<tr>
<td>Alberta / Inuvik, NWT</td>
<td>Mountain Standard Time</td>
<td>Canada Central Standard Time</td>
<td>UTC-06:00</td>
</tr>
<tr>
<td>Manitoba</td>
<td>Central Standard Time</td>
<td>Eastern Standard Time (Mexico)</td>
<td>UTC-05:00</td>
</tr>
</tbody>
</table>
<p>You can make the change in the Google Cloud console (<strong>Edit instance</strong> &gt; <strong>Flags and parameters</strong> &gt; <strong>Time zone</strong>) or with gcloud:</p>
<pre class="prettyprint lang-bash"><code>gcloud sql instances patch INSTANCE_NAME \
  --project=PROJECT_ID \
  --time-zone="Yukon Standard Time"
</code></pre>
]]>
    </content>
  </entry>

  <entry>
    <title>October 28, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_28_2026</id>
    <updated>2026-10-28T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_28_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/mysql/replication/read-replica-indexes#managed-replica-indexes">Managed replica indexes</a>
for Cloud SQL for MySQL are generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>). This feature
lets you automatically retain and restore secondary indexes on read replica
instances when Cloud SQL re-creates a replica.</p>
<p>Previously, re-creating a read replica deleted custom secondary indexes because
primary backups don't have replica-only index definitions. With managed replica
indexes, Cloud SQL tracks secondary index metadata on the primary instance,
replicates this metadata to read replicas, and automatically rebuilds secondary
indexes after replica re-creation.</p>
<p>Managed replica indexes are supported on instances that are
running Cloud SQL for MySQL 8.0 or later,
Cloud SQL Enterprise edition or Cloud SQL Enterprise Plus edition,
and maintenance version <code>R20260726.00_05</code> or later.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/replication/read-replica-indexes">Read replica indexes overview</a>
and
<a href="https://docs.cloud.google.com/sql/docs/mysql/replication/create-manage-read-replica-indexes">Create and manage read replica indexes</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 23, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_23_2026</id>
    <updated>2026-10-23T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_23_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Security</h3>
<p>In response to <a href="https://docs.cloud.google.com/support/bulletins#gcp-2026-071">GCP-2026-071</a>, Google is
updating Cloud SQL's managed components. No manual updates to the certificate
store are required for Cloud SQL-managed instances. The fix is shipping in a
new maintenance version that will be applied during
<a href="https://docs.cloud.google.com/sql/docs/mysql/maintenance">scheduled maintenance</a>. You can also apply the
fix by <a href="https://docs.cloud.google.com/sql/docs/mysql/self-service-maintenance">performing self-service
maintenance</a>. An announcement will
be published when the self-service maintenance fix is available.</p>
<p><strong>What should I do?</strong></p>
<ul>
<li><p>If you use the Cloud SQL Auth Proxy, then upgrade the Cloud SQL Auth Proxy to
<a href="https://docs.cloud.google.com/sql/docs/mysql/sql-proxy#install">2.26.3 or later</a> and the Cloud SQL Proxy
Operator to <a href="https://docs.cloud.google.com/sql/docs/mysql/connect-proxy-operator">1.8.4 or later</a>. If you
run the standalone proxy binary, then also update the host's certificate
authority (CA) certificates.</p></li>
<li><p>If you use a Cloud SQL Language Connector, then update the language runtime
and operating system CA certificates used with the
<a href="https://docs.cloud.google.com/sql/docs/mysql/connect-connectors">Cloud SQL Language Connector</a> (for
example, Go 1.26.10 or 1.27.3 or later, certifi 2026.10.19 or later).</p></li>
<li><p>If you're using the gcloud CLI to install the Cloud SQL Auth Proxy, then
update the gcloud CLI to <a href="https://docs.cloud.google.com/sdk/gcloud#download_and_install_the">590.0.1</a>.</p></li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Security</h3>
<p>In response to <a href="https://docs.cloud.google.com/support/bulletins#gcp-2026-071">GCP-2026-071</a>, Google is
updating Cloud SQL's managed components. No manual updates to the certificate
store are required for Cloud SQL-managed instances. The fix is shipping in a
new maintenance version that will be applied during
<a href="https://docs.cloud.google.com/sql/docs/postgres/maintenance">scheduled maintenance</a>. You can also apply
the fix by <a href="https://docs.cloud.google.com/sql/docs/postgres/self-service-maintenance">performing self-service
maintenance</a>. An announcement
will be published when the self-service maintenance fix is available.</p>
<p><strong>What should I do?</strong></p>
<ul>
<li><p>If you use the Cloud SQL Auth Proxy, then upgrade the Cloud SQL Auth Proxy to
<a href="https://docs.cloud.google.com/sql/docs/postgres/sql-proxy#install">2.26.3 or later</a> and the Cloud SQL
Proxy Operator to
<a href="https://docs.cloud.google.com/sql/docs/postgres/connect-proxy-operator">1.8.4 or later</a>. If you run the
standalone proxy binary, then also update the host's certificate authority
(CA) certificates.</p></li>
<li><p>If you use a Cloud SQL Language Connector, then update the language runtime
and operating system CA certificates used with the
<a href="https://docs.cloud.google.com/sql/docs/postgres/connect-connectors">Cloud SQL Language Connector</a> (for
example, Go 1.26.10 or 1.27.3 or later, certifi 2026.10.19 or later).</p></li>
<li><p>If you're using the gcloud CLI to install the Cloud SQL Auth Proxy, then
update the gcloud CLI to <a href="https://docs.cloud.google.com/sdk/gcloud#download_and_install_the">590.0.1</a>.</p></li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Security</h3>
<p>In response to <a href="https://docs.cloud.google.com/support/bulletins#gcp-2026-071">GCP-2026-071</a>, Google is
updating Cloud SQL's managed components. No manual updates to the certificate
store are required for Cloud SQL-managed instances. The fix is shipping in a
new maintenance version that will be applied during
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/maintenance">scheduled maintenance</a>. You can also apply
the fix by <a href="https://docs.cloud.google.com/sql/docs/sqlserver/self-service-maintenance">performing self-service
maintenance</a>. An announcement
will be published when the self-service maintenance fix is available.</p>
<p><strong>What should I do?</strong></p>
<ul>
<li><p>If you use the Cloud SQL Auth Proxy, then upgrade the Cloud SQL Auth Proxy to
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/sql-proxy#install">2.26.3 or later</a> and the Cloud SQL
Proxy Operator to
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/connect-proxy-operator">1.8.4 or later</a>. If you run the
standalone proxy binary, then also update the host's certificate authority
(CA) certificates.</p></li>
<li><p>If you use a Cloud SQL Language Connector, then update the language runtime
and operating system CA certificates used with the
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/connect-connectors">Cloud SQL Language Connector</a> (for
example, Go 1.26.10 or 1.27.3 or later, certifi 2026.10.19 or later).</p></li>
<li><p>If you're using the gcloud CLI to install the Cloud SQL Auth Proxy, then
update the gcloud CLI to <a href="https://docs.cloud.google.com/sdk/gcloud#download_and_install_the">590.0.1</a>.</p></li>
</ul>
]]>
    </content>
  </entry>

  <entry>
    <title>October 16, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_16_2026</id>
    <updated>2026-10-16T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_16_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>Cloud SQL for PostgreSQL now supports enabling <a href="https://docs.cloud.google.com/sql/docs/postgres/managed-connection-pooling">Managed Connection Pooling</a>
on existing <a href="https://docs.cloud.google.com/sql/docs/postgres/about-private-service-connect">Private Service Connect</a>
instances. Previously, Cloud SQL supported enabling Managed Connection Pooling only
on new instances using Private Service Connect.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/managed-connection-pooling">Managed Connection Pooling overview</a>
and <a href="https://docs.cloud.google.com/sql/docs/postgres/configure-mcp">Configure Managed Connection Pooling</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 14, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_14_2026</id>
    <updated>2026-10-14T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_14_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Issue</h3>
<p>When you enable the <a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
integration on a Cloud SQL for MySQL instance created before April 18, 2026,
the integration defaults to once a day instead of near real-time.</p>
<p>Near real-time updates upon Knowledge Catalog enablement aren't yet available for
all existing instances. A new announcement will be published when this feature
becomes available.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Issue</h3>
<p>When you enable the <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
integration on a Cloud SQL for PostgreSQL instance created before April 18, 2026,
the integration defaults to once a day instead of near real-time.</p>
<p>Near real-time updates upon Knowledge Catalog enablement aren't yet available for
all existing instances. A new announcement will be published when this feature
becomes available.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 13, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_13_2026</id>
    <updated>2026-10-13T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_13_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/mysql/about-private-service-connect">Private Service Connect</a> is now
the default private IP connectivity option when you create a Cloud SQL for MySQL
instance in a new Google Cloud project. Private Service Connect lets you connect
to your instance from multiple Virtual Private Cloud (VPC) networks across
different groups, projects, or organizations, and supports automatic endpoint
and DNS record provisioning. When you configure private IP for an instance, you
can still choose to use private services access or both connectivity options.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/private-ip">Private IP configuration options</a> and
<a href="https://docs.cloud.google.com/sql/docs/mysql/configure-private-service-connect">Configure Private Service Connect</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/postgres/about-private-service-connect">Private Service Connect</a> is
now the default private IP connectivity option when you create a Cloud SQL for
PostgreSQL instance in a new Google Cloud project. Private Service Connect lets
you connect to your instance from multiple Virtual Private Cloud (VPC) networks
across different groups, projects, or organizations, and supports automatic
endpoint and DNS record provisioning. When you configure private IP for an
instance, you can still choose to use private services access or both
connectivity options.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/private-ip">Private IP configuration options</a> and
<a href="https://docs.cloud.google.com/sql/docs/postgres/configure-private-service-connect">Configure Private Service Connect</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/sqlserver/about-private-service-connect">Private Service Connect</a> is
now the default private IP connectivity option when you create a Cloud SQL for
SQL Server instance in a new Google Cloud project. Private Service Connect lets
you connect to your instance from multiple Virtual Private Cloud (VPC) networks
across different groups, projects, or organizations, and supports automatic
endpoint and DNS record provisioning. When you configure private IP for an
instance, you can still choose to use private services access or both
connectivity options.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/sqlserver/private-ip">Private IP configuration options</a> and
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/configure-private-service-connect">Configure Private Service Connect</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 10, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_10_2026</id>
    <updated>2026-10-10T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_10_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Change</h3>
<p>MySQL 8.0.46 is now the
<a href="https://docs.cloud.google.com/sql/docs/mysql/db-versions#database-version-support">default minor version</a>
for Cloud SQL for MySQL 8.0.</p>
<p>For more information about minor version support in Cloud SQL for MySQL,
see <a href="https://docs.cloud.google.com/sql/docs/mysql/db-versions#mysql-8.0">MySQL 8.0</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 09, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_09_2026</id>
    <updated>2026-10-09T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_09_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<aside class="note">
<b>Note:</b> Near real-time sync upon Knowledge Catalog (KC) enablement isn't available for existing instances created before April 18, 2026. For more information, see the <a href="#October_14_2026">release note from October 14, 2026</a>.
</aside>
<p>When you enable <a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
integration on an eligible Cloud SQL for MySQL instance created before April 18,
2026 where the integration is currently turned off, the instance now syncs schema
and metadata updates to Knowledge Catalog in near real-time instead of once a day
(instances created on or after April 18, 2026 have near real-time sync enabled by
default).</p>
<p>This feature is available for instances running MySQL version 8.0 or later on the
<a href="https://docs.cloud.google.com/sql/docs/mysql/upgrade-cloud-sql-instance-new-network-architecture#overview">new network architecture</a>.
If Knowledge Catalog integration is already enabled on the instance with
once-a-day updates, you can <a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration#deactivate-dataplex-catalog">deactivate</a>
and re-enable the integration to switch to near real-time updates.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/dataplex-catalog-integration#enable-dataplex-catalog">Enable the integration of Knowledge Catalog on an existing Cloud SQL instance</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<aside class="note">
<b>Note:</b> Near real-time sync upon Knowledge Catalog (KC) enablement isn't available for existing instances created before April 18, 2026. For more information, see the <a href="#October_14_2026">release note from October 14, 2026</a>.
</aside>
<p>When you enable <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
integration on an eligible Cloud SQL for PostgreSQL instance created before
April 18, 2026 where the integration is currently turned off, the instance now
syncs schema and metadata updates to Knowledge Catalog in near real-time instead
of once a day (instances created on or after April 18, 2026 have near real-time
sync enabled by default).</p>
<p>This feature is available for instances running PostgreSQL version 14.0 or later
on the <a href="https://docs.cloud.google.com/sql/docs/postgres/upgrade-cloud-sql-instance-new-network-architecture#overview">new network architecture</a>.
If Knowledge Catalog integration is already enabled on the instance with
once-a-day updates, you can <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration#deactivate-dataplex-catalog">deactivate</a>
and re-enable the integration to switch to near real-time updates.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration#enable-dataplex-catalog">Enable the integration of Knowledge Catalog on an existing Cloud SQL instance</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 08, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_08_2026</id>
    <updated>2026-10-08T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_08_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>Cloud SQL for MySQL now supports the
<code>innodb_cloudsql_managed_buffer_pool_tuneup_pct</code> database flag.</p>
<p>Managed buffer pool automatically adjusts the InnoDB buffer pool size to reduce
out-of-memory events. When instance memory usage remains at or below 70% for 10
minutes or longer after prior reductions, Cloud SQL increases the buffer pool
size. You can now use the <code>innodb_cloudsql_managed_buffer_pool_tuneup_pct</code> flag
to change this 70% threshold to a different percentage. Increase the threshold
to restore the InnoDB buffer pool size when baseline usage exceeds 70%, or
decrease it to preserve additional RAM allocation for memory spikes.</p>
<p>This flag requires the Cloud SQL maintenance version
<a href="https://docs.cloud.google.com/sql/docs/mysql/maintenance-changelog"><i>MYSQL_VERSION</i>.R20260726.00_05</a>
or later. For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/optimize-high-memory-usage#enable-managed-buffer-pool">Enable managed buffer
pool</a>.</p>
<h3>Feature</h3>
<p>Cloud SQL for MySQL supports blue-green deployments
(<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>).</p>
<p>Blue-green deployments let you update databases—such as performing major
version upgrades from MySQL 8.0 to 8.4 and staging hardware or configuration
modifications—while minimizing downtime. During a blue-green deployment,
Cloud SQL creates a separate staging environment (green) that mirrors your
existing production environment (blue) and maintains continuous logical
replication from blue to green. You can test application compatibility and
performance on the green environment without affecting production traffic, and
then trigger a switchover to the green environment with minimal application
downtime.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/about-blue-green-deployments">About blue-green deployments in
Cloud SQL</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 06, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#October_06_2026</id>
    <updated>2026-10-06T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#October_06_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Change</h3>
<p>Cloud SQL for MySQL now supports up to 100,000 concurrent connections for
Private Service Connect enabled instances created on or after September 30, 2026
with 16 or more vCPUs.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/configure-private-service-connect#limitations">Configure Private Service Connect</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>Cloud SQL for PostgreSQL now supports up to 129,024 concurrent connections for
Private Service Connect enabled instances created on or after September 30, 2026
with 16 or more vCPUs.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/configure-private-service-connect#limitations">Configure Private Service Connect</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 29, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_29_2026</id>
    <updated>2026-09-29T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_29_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>You can use the pgAudit extension to prevent string literals that might indicate
sensitive information, such as passwords and secrets, from appearing in your log
query results. This release provides minor bug fixes to the previous version.</p>
<p>This pgAudit extension capability is supported on
<code>[PostgreSQL version].R20260712.01_RC31</code> or later.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/pg-audit">Audit for PostgreSQL using pgAudit</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 28, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_28_2026</id>
    <updated>2026-09-28T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_28_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Breaking</h3>
<p>To improve security, removed the <code>cloudsql.instances.export</code> permission
from the following roles:</p>
<ul>
<li>Cloud SQL Viewer (<code>roles/cloudsql.viewer</code>)</li>
<li>Basic Reader (<code>roles/reader</code>)</li>
<li>Basic Viewer (Legacy) (<code>roles/viewer</code>)</li>
</ul>
<p>To retain export capabilities, assign the Cloud SQL Editor
(<code>roles/cloudsql.editor</code>) role or update custom roles to include the
<code>cloudsql.instances.export</code> permission.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/iam-roles">Cloud SQL roles</a>.</p>
<h3>Change</h3>
<p>Cloud SQL for MySQL 9.7.1 is upgraded to MySQL 9.7.2. For more information, see
the <a href="https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-2.html">MySQL 9.7.2 Release Notes</a>
and <a href="https://docs.cloud.google.com/sql/docs/mysql/db-versions">Cloud SQL database versions</a>.</p>
<h3>Change</h3>
<p>Cloud SQL for MySQL 8.4.10 is upgraded to MySQL 8.4.11. For more information,
see the <a href="https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-11.html">MySQL 8.4.11 Release Notes</a>
and <a href="https://docs.cloud.google.com/sql/docs/mysql/db-versions">Cloud SQL database versions</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Breaking</h3>
<p>To improve security, removed the <code>cloudsql.instances.export</code> permission
from the following roles:</p>
<ul>
<li>Cloud SQL Viewer (<code>roles/cloudsql.viewer</code>)</li>
<li>Basic Reader (<code>roles/reader</code>)</li>
<li>Basic Viewer (Legacy) (<code>roles/viewer</code>)</li>
</ul>
<p>To retain export capabilities, assign the Cloud SQL Editor
(<code>roles/cloudsql.editor</code>) role or update custom roles to include the
<code>cloudsql.instances.export</code> permission.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/iam-roles">Cloud SQL roles</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Breaking</h3>
<p>To improve security, removed the <code>cloudsql.instances.export</code> permission
from the following roles:</p>
<ul>
<li>Cloud SQL Viewer (<code>roles/cloudsql.viewer</code>)</li>
<li>Basic Reader (<code>roles/reader</code>)</li>
<li>Basic Viewer (Legacy) (<code>roles/viewer</code>)</li>
</ul>
<p>To retain export capabilities, assign the Cloud SQL Editor
(<code>roles/cloudsql.editor</code>) role or update custom roles to include the
<code>cloudsql.instances.export</code> permission.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/iam-roles">Cloud SQL roles</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 21, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_21_2026</id>
    <updated>2026-09-21T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_21_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/mysql/machine-series-overview.md#c4">C4 machine series</a>
is available for Cloud SQL for MySQL Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>asia-east2</code> — Hong Kong</li>
<li><code>asia-southeast2</code> — Jakarta, Indonesia</li>
<li><code>europe-west3</code> — Frankfurt, Germany</li>
<li><code>europe-west4</code> — Eemshaven, Netherlands</li>
<li><code>europe-west8</code> — Milan, Italy</li>
<li><code>us-east5</code> — Columbus, Ohio, USA</li>
<li><code>us-south1</code> — Dallas, Texas, USA</li>
<li><code>us-west4</code> — Las Vegas, Nevada, USA</li>
</ul>
<p>The C4 machine series provides the following benefits:</p>
<ul>
<li>Supports fifth and sixth generation Intel Xeon Scalable processors.</li>
<li>Offers a price-performance balance that makes it suitable for
high-demand workloads.</li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/postgres/machine-series-overview.md#c4">C4 machine series</a>
is available for Cloud SQL for PostgreSQL Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>asia-east2</code> — Hong Kong</li>
<li><code>asia-southeast2</code> — Jakarta, Indonesia</li>
<li><code>europe-west3</code> — Frankfurt, Germany</li>
<li><code>europe-west4</code> — Eemshaven, Netherlands</li>
<li><code>europe-west8</code> — Milan, Italy</li>
<li><code>us-east5</code> — Columbus, Ohio, USA</li>
<li><code>us-south1</code> — Dallas, Texas, USA</li>
<li><code>us-west4</code> — Las Vegas, Nevada, USA</li>
</ul>
<p>The C4 machine series provides the following benefits:</p>
<ul>
<li>Supports fifth and sixth generation Intel Xeon Scalable processors.</li>
<li>Offers a price-performance balance that makes it suitable for
high-demand workloads.</li>
</ul>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md#c4">C4 machine series</a>
is available for Cloud SQL for SQL Server Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>asia-east2</code> — Hong Kong</li>
<li><code>asia-southeast2</code> — Jakarta, Indonesia</li>
<li><code>europe-west3</code> — Frankfurt, Germany</li>
<li><code>europe-west4</code> — Eemshaven, Netherlands</li>
<li><code>europe-west8</code> — Milan, Italy</li>
<li><code>us-east5</code> — Columbus, Ohio, USA</li>
<li><code>us-south1</code> — Dallas, Texas, USA</li>
<li><code>us-west4</code> — Las Vegas, Nevada, USA</li>
</ul>
<p>The C4 machine series provides the following benefits:</p>
<ul>
<li>Supports fifth and sixth generation Intel Xeon Scalable processors.</li>
<li>Offers a price-performance balance that makes it suitable for
high-demand workloads.</li>
</ul>
]]>
    </content>
  </entry>

  <entry>
    <title>September 17, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_17_2026</id>
    <updated>2026-09-17T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_17_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Change</h3>
<p>Cloud SQL for MySQL now automatically enables point-in-time recovery (PITR) in
a separate, asynchronous operation after disaster recovery (DR) switchover and
replica failover operations complete. Because PITR enablement no longer blocks
switchover and replica failover, these operations complete faster, helping you
reduce your recovery time.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery">Use advanced disaster recovery (DR)</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>Cloud SQL for PostgreSQL now automatically enables point-in-time recovery
(PITR) in a separate, asynchronous operation after disaster recovery (DR)
switchover and replica failover operations complete. Because PITR enablement no
longer blocks switchover and replica failover, these operations complete faster,
helping you reduce your recovery time.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/use-advanced-disaster-recovery">Use advanced disaster recovery (DR)</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 14, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_14_2026</id>
    <updated>2026-09-14T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_14_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>You can use the
<a href="https://github.com/timescale/pg_textsearch"><code>pg_textsearch</code></a>
extension in Cloud SQL for PostgreSQL to perform full-text search using the
industry-standard
<a href="https://en.wikipedia.org/wiki/Okapi_BM25">BM25 (Best Matching 25)</a> scoring
algorithm for highly accurate relevance scoring.</p>
<p>This extension requires PostgreSQL 17 or later and is supported on PostgreSQL
release <code>R20260712.01_06</code> or later.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/pg-textsearch">Full-text search using pg_textsearch</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Deprecated</h3>
<p>Beginning April 12, 2027, you won't be able to create new instances of
Cloud SQL for SQL Server 2017. Starting on October 13, 2027, SQL Server 2017
will reach end of life (EOL) and Microsoft will stop releasing
<a href="https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview?view=sql-server-ver17#understand-the-sql-server-lifecycle">security updates</a>.
Cloud SQL for SQL Server will stop supporting SQL Server 2017 after this date.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/db-versions">Database versions and version policies</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 10, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_10_2026</id>
    <updated>2026-09-10T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_10_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Breaking</h3>
<p>Appending <code>sqlcommenter</code> tags using the <code>sql_commenter_enabled</code> parameter when
executing SQL queries on a Cloud SQL remote MCP server is temporarily disabled.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/use-cloudsql-mcp#sqlcommenter">sqlcommenter tags</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Breaking</h3>
<p>Appending <code>sqlcommenter</code> tags using the <code>sql_commenter_enabled</code> parameter when
executing SQL queries on a Cloud SQL remote MCP server is temporarily disabled.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/use-cloudsql-mcp#sqlcommenter">sqlcommenter tags</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 08, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_08_2026</id>
    <updated>2026-09-08T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_08_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/mysql/admin-api/rep">Regional endpoints (REP)</a>
are now generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>)
for the Cloud SQL for MySQL Admin API.</p>
<p>Regional endpoints let you interact with Cloud SQL for MySQL instances
using regionalized URLs (such as
<code>sqladmin.<a href="https://docs.cloud.google.com/sql/docs/mysql/admin-api/rep#supported_regions">{region}</a>.rep.googleapis.com</code>)
rather than through a single global endpoint.</p>
<p>Regional endpoints provide regional frontend and load balancing infrastructure
that improves data residency by keeping network traffic within the same
region as the instance. This reduces the instance's dependency on global
frontend infrastructure.</p>
<p>Regional endpoints have strong regional isolation, so the failure of a load
balancer or frontend in one region doesn't affect any other
region. Regional service load balancers have a separate, regionally
isolated control plane.</p>
<p>Regional endpoints are designed to meet stringent data residency and
sovereignty standards, such as ITAR and Assured Workloads Regions, ensuring
data in transit remains within the committed region.</p>
<p>Certificate management and TLS termination occurs within each region, on the
regional load balancer, so data remains encrypted until it reaches its
destination region and stays within that region while being processed there.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/postgres/admin-api/rep">Regional endpoints (REP)</a>
are now generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>)
for the Cloud SQL for PostgreSQL Admin API.</p>
<p>Regional endpoints let you interact with Cloud SQL for PostgreSQL instances
using regionalized URLs (such as
<code>sqladmin.<a href="https://docs.cloud.google.com/sql/docs/postgres/admin-api/rep#supported_regions">{region}</a>.rep.googleapis.com</code>)
rather than through a single global endpoint.</p>
<p>Regional endpoints provide regional frontend and load balancing infrastructure
that improves data residency by keeping network traffic within the same
region as the instance. This reduces the instance's dependency on global
frontend infrastructure.</p>
<p>Regional endpoints have strong regional isolation, so the failure of a load
balancer or frontend in one region doesn't affect any other
region. Regional service load balancers have a separate, regionally
isolated control plane.</p>
<p>Regional endpoints are designed to meet stringent data residency and
sovereignty standards, such as ITAR and Assured Workloads Regions, ensuring
data in transit remains within the committed region.</p>
<p>Certificate management and TLS termination occurs within each region, on the
regional load balancer, so data remains encrypted until it reaches its
destination region and stays within that region while being processed there.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/rep">Regional endpoints (REP)</a>
are now generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>)
for the Cloud SQL for SQL Server Admin API.</p>
<p>Regional endpoints let you interact with Cloud SQL for SQL Server instances
using regionalized URLs (such as
<code>sqladmin.<a href="https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/rep#supported_regions">{region}</a>.rep.googleapis.com</code>)
rather than through a single global endpoint.</p>
<p>Regional endpoints provide regional frontend and load balancing infrastructure
that improves data residency by keeping network traffic within the same
region as the instance. This reduces the instance's dependency on global
frontend infrastructure.</p>
<p>Regional endpoints have strong regional isolation, so the failure of a load
balancer or frontend in one region doesn't affect any other
region. Regional service load balancers have a separate, regionally
isolated control plane.</p>
<p>Regional endpoints are designed to meet stringent data residency and
sovereignty standards, such as ITAR and Assured Workloads Regions, ensuring
data in transit remains within the committed region.</p>
<p>Certificate management and TLS termination occurs within each region, on the
regional load balancer, so data remains encrypted until it reaches its
destination region and stays within that region while being processed there.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 04, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_04_2026</id>
    <updated>2026-09-04T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_04_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/mysql/machine-series-overview.md#c4">C4 machine series</a>
is now available for Cloud SQL for MySQL Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>africa-south1</code> — Johannesburg</li>
<li><code>asia-northeast3</code> — Seoul</li>
<li><code>asia-south2</code> — Delhi</li>
<li><code>europe-west6</code> — Zürich</li>
<li><code>southamerica-west1</code> — Santiago</li>
<li><code>us-west3</code> — Salt Lake City</li>
</ul>
<p>The C4 machine series provides the following benefits:</p>
<ul>
<li>Supports fifth and sixth generation Intel Xeon Scalable processors.</li>
<li>Offers a price-performance balance that makes it suitable for
high-demand workloads.</li>
</ul>
<h3>Feature</h3>
<p>Cloud SQL supports in-place upgrades and downgrades to your instance's
infrastructure. You can change all of the following in place:</p>
<ul>
<li>The edition that your Cloud SQL instance uses.</li>
<li>The machine type.</li>
<li>The storage type.</li>
<li>The database version.</li>
</ul>
<p>Making in-place changes is the most direct and least error-prone way to
reconfigure an instance.</p>
<p>For more information about in-place upgrades and downgrades, see
<a href="https://docs.cloud.google.com/sql/docs/mysql/upgrade-in-place">Upgrade in place</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/postgres/machine-series-overview.md#c4">C4 machine series</a>
is now available for Cloud SQL for PostgreSQL Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>africa-south1</code> — Johannesburg</li>
<li><code>asia-northeast3</code> — Seoul</li>
<li><code>asia-south2</code> — Delhi</li>
<li><code>europe-west6</code> — Zürich</li>
<li><code>southamerica-west1</code> — Santiago</li>
<li><code>us-west3</code> — Salt Lake City</li>
</ul>
<p>The C4 machine series provides the following benefits:</p>
<ul>
<li>Supports fifth and sixth generation Intel Xeon Scalable processors.</li>
<li>Offers a price-performance balance that makes it suitable for
high-demand workloads.</li>
</ul>
<h3>Feature</h3>
<p>Cloud SQL supports in-place upgrades and downgrades to your instance's
infrastructure. You can change all of the following in place:</p>
<ul>
<li>The edition that your Cloud SQL instance uses.</li>
<li>The machine type.</li>
<li>The storage type.</li>
<li>The database version.</li>
</ul>
<p>Making in-place changes is the most direct and least error-prone way to
reconfigure an instance.</p>
<p>For more information about in-place upgrades and downgrades, see
<a href="https://docs.cloud.google.com/sql/docs/postgres/upgrade-in-place">Upgrade in place</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>Cloud SQL for SQL Server supports the <code>sp_help_revlogin</code> stored procedure in
the <code>msdb</code> database. You can enable this stored procedure by configuring the
<code>cloud sql enable sp_help_revlogin</code> database flag to export SQL Server logins,
password hashes, and security identifiers (SIDs) when migrating databases or
synchronizing logins.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/export-logins">Export SQL Server logins</a> and
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/flags">Configure database flags</a>.</p>
<h3>Feature</h3>
<p>Cloud SQL for SQL Server now supports connecting to instances
with write endpoints using the Cloud SQL Auth Proxy or Cloud SQL language
connectors. When you configure the proxy or a language connector with a
write endpoint DNS name, connections are redirected automatically to the new
primary instance during replica failover or switchover.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/connect-to-instance-using-write-endpoint">Connect to an instance using a write endpoint</a>.</p>
<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md#c4">C4 machine series</a>
is now available for Cloud SQL for SQL Server Enterprise Plus instances in the
following regions:</p>
<ul>
<li><code>africa-south1</code> — Johannesburg</li>
<li><code>asia-northeast3</code> — Seoul</li>
<li><code>asia-south2</code> — Delhi</li>
<li><code>europe-west6</code> — Zürich</li>
<li><code>southamerica-west1</code> — Santiago</li>
<li><code>us-west3</code> — Salt Lake City</li>
</ul>
<p>The C4 machine series provides the following benefits:</p>
<ul>
<li>Supports fifth and sixth generation Intel Xeon Scalable processors.</li>
<li>Offers a price-performance balance that makes it suitable for
high-demand workloads.</li>
</ul>
<h3>Feature</h3>
<p>Cloud SQL supports in-place upgrades and downgrades to your instance's
infrastructure. You can change all of the following in place:</p>
<ul>
<li>The edition that your Cloud SQL instance uses.</li>
<li>The machine type.</li>
<li>The storage type.</li>
<li>The database version.</li>
</ul>
<p>Making in-place changes is the most direct and least error-prone way to
reconfigure an instance.</p>
<p>For more information about in-place upgrades and downgrades, see
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/upgrade-in-place">Upgrade in place</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>September 02, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#September_02_2026</id>
    <updated>2026-09-02T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#September_02_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>Cloud SQL supports Workforce Identity Federation authentication. This lets you
authenticate to your Cloud SQL instance using identities from an external
identity provider such as Microsoft Active Directory or Okta. For more
information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/workforce-authentication">Workforce Identity Federation
authentication</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>Cloud SQL supports Workforce Identity Federation authentication. This lets you
authenticate to your Cloud SQL instance using identities from an external
identity provider such as Microsoft Active Directory or Okta. For more
information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/workforce-authentication">Workforce Identity Federation
authentication</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>August 31, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#August_31_2026</id>
    <updated>2026-08-31T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#August_31_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>You can use the pgAudit extension to prevent string literals that might indicate
sensitive information, such as passwords and secrets, from appearing in your log
query results.</p>
<p>This pgAudit extension capability is supported on
<code>[PostgreSQL version].R20260712.01_06</code> or later.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/pg-audit">Audit for PostgreSQL using pgAudit</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>August 27, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#August_27_2026</id>
    <updated>2026-08-27T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#August_27_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>Cloud SQL now makes it easier to configure <a href="https://docs.cloud.google.com/sql/docs/mysql/about-private-service-connect">Private Service Connect</a> for your
Cloud SQL instance. When you create an
instance that's enabled with
Private Service Connect, you can choose to automatically create
the service connection policy and endpoint in the VPC network
that you want to use with Private Service Connect.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/configure-private-service-connect">Configure Private Service Connect</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>The rollout of the following extension upgrades is complete:</p>
<ul>
<li><code>pg_partman</code> is upgraded from 5.2.4 to 5.4.3.</li>
<li><code>pgfincore</code> is upgraded from 1.3.1 to 1.4.</li>
<li><code>pgvector</code> is upgraded from 0.8.1 to 0.8.5.</li>
</ul>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/extensions">Configure PostgreSQL extensions</a>.</p>
<h3>Feature</h3>
<p>Cloud SQL now makes it easier to configure <a href="https://docs.cloud.google.com/sql/docs/postgres/about-private-service-connect">Private Service Connect</a> for your
Cloud SQL instance. When you create an
instance that's enabled with
Private Service Connect, you can choose to automatically create
the service connection policy and endpoint in the VPC network
that you want to use with Private Service Connect.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/configure-private-service-connect">Configure Private Service Connect</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>Cloud SQL now makes it easier to configure <a href="https://docs.cloud.google.com/sql/docs/sqlserver/about-private-service-connect">Private Service Connect</a> for your
Cloud SQL instance. When you create an
instance that's enabled with
Private Service Connect, you can choose to automatically create
the service connection policy and endpoint in the VPC network
that you want to use with Private Service Connect.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/sqlserver/configure-private-service-connect">Configure Private Service Connect</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>August 25, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#August_25_2026</id>
    <updated>2026-08-25T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#August_25_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>Use assessments
(<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>)
in <a href="https://docs.cloud.google.com/database-center/docs/overview">Database Center</a> to assess and test the
performance impact of database recommendations before you apply them to your
production database fleet.</p>
<p>The assessments workflow performs these operations:</p>
<ul>
<li>Clones your database instance.</li>
<li>Runs benchmarking simulation tests on the clone.</li>
<li>Compares the baseline performance of the clone against the performance after
you apply the recommended configuration changes.</li>
</ul>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/assessments-overview">Assessments in Database Center</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>August 13, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#August_13_2026</id>
    <updated>2026-08-13T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#August_13_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/sql/docs/mysql/db-versions">Cloud SQL for MySQL 9.7</a> is generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>).</p>
<p>For more information about the differences between MySQL 9.7 and previous
versions, review the <a href="https://dev.mysql.com/doc/relnotes/mysql/9.7/en/">MySQL 9.7 Release Notes</a>.</p>
<p>By default, if you specify MySQL 9.7 as the version when you create a Cloud SQL
instance (either primary or replica) using the gcloud CLI, the Google Cloud
console, or the REST API, then the Cloud SQL edition is Cloud SQL Enterprise Plus
edition.</p>
<p>This release introduces support for key MySQL 9.7 capabilities, including:</p>
<ul>
<li><a href="https://docs.cloud.google.com/sql/docs/mysql/vector-search#version-differences"><strong>Vector search</strong></a>: support
for the community-standard vector storage format
combined with advanced approximate nearest neighbor (ANN) vector
indexing in Cloud SQL.</li>
<li><a href="https://blogs.oracle.com/mysql/the-hypergraph-optimizer-is-now-available-in-mysql-9-7-community-edition"><strong>Hypergraph optimizer</strong></a>:
an alternative join-planning framework designed for
complex, multi-table queries. You can enable the hypergraph optimizer using an
<a href="https://dev.mysql.com/doc/refman/9.7/en/switchable-optimizations.html">optimizer switch</a>.</li>
<li><a href="https://dev.mysql.com/doc/refman/9.7/en/json-duality-views.html"><strong>JSON Duality Views</strong></a>:
a feature that bridges relational SQL and hierarchical
JSON document models to interact with the same underlying data.</li>
<li><strong>Upgrade and migration paths</strong>: support for <a href="https://docs.cloud.google.com/sql/docs/mysql/upgrade-major-db-version-inplace">in-place major version upgrade</a>
from Cloud SQL for MySQL 8.4 and
<a href="https://docs.cloud.google.com/database-migration/docs/mysql/migration-src-and-dest#cross-version-support">migrations from MySQL 8.4 using the Database Migration Service (DMS)</a>.</li>
</ul>
<aside class="note"><strong>Note:</strong><span> The legacy <code>mysql_native_password</code> authentication plugin is no longer
supported starting in Cloud SQL for MySQL 9.7. You must update all clients that
use built-in authentication user accounts to use the <code>caching_sha2_password</code> plugin
instead. For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/features#mysql-authentication">MySQL authentication</a>.</span></aside>
<h3 id="flag_updates_for_mysql_97">Flag updates for MySQL 9.7</h3>
<p>Additionally, this release introduces several database flag changes.</p>
<table>
<thead>
<tr>
<th>MySQL database flag</th>
<th>Action</th>
<th>Details</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>activate_mandatory_roles</code></td>
<td>Added / Supported</td>
<td>Exposes mandatory roles configuration. Default is ON.</td>
</tr>
<tr>
<td><code>innodb_native_foreign_keys</code></td>
<td>Added / Supported</td>
<td>Exposes SQL layer foreign key handling configuration.</td>
</tr>
<tr>
<td><code>table_open_cache_triggers</code></td>
<td>Added / Supported</td>
<td>Configures trigger cache size limits.</td>
</tr>
<tr>
<td><code>connection_memory_status_limit</code></td>
<td>Added / Supported</td>
<td>Sets limit configurations on connection memory.</td>
</tr>
<tr>
<td><code>global_connection_memory_status_limit</code></td>
<td>Added / Supported</td>
<td>Sets global limit configurations on connection memory.</td>
</tr>
<tr>
<td><code>performance_schema_max_logger_classes</code></td>
<td>Added / Supported</td>
<td>Sets limits for performance schema logger classes.</td>
</tr>
<tr>
<td><code>caching_sha2_password_proxy_users</code></td>
<td>Added / Supported</td>
<td>Configures proxy users support for caching SHA-2.</td>
</tr>
<tr>
<td><code>caching_sha2_password_enforce_storage_format</code></td>
<td>Added / Supported</td>
<td>Enforces storage format rules for caching SHA-2.</td>
</tr>
<tr>
<td><code>caching_sha2_password_storage_format</code></td>
<td>Added / Supported</td>
<td>Sets storage format defaults for caching SHA-2.</td>
</tr>
<tr>
<td><code>innodb_log_file_size</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
<tr>
<td><code>innodb_log_files_in_group</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
<tr>
<td><code>innodb_undo_tablespaces</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
<tr>
<td><code>mysql_native_password_proxy_users</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
<tr>
<td><code>replica_parallel_type</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
<tr>
<td><code>slave_parallel_type</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
<tr>
<td><code>temptable_use_mmap</code></td>
<td>Removed</td>
<td>Flag not supported in MySQL 9.7 and later.</td>
</tr>
</tbody>
</table>
<p>For more information about MySQL database flags, see <a href="https://docs.cloud.google.com/sql/docs/mysql/flags">Configure database flags</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>August 11, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#August_11_2026</id>
    <updated>2026-08-11T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#August_11_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for MySQL</h2>
<h3>Feature</h3>
<p>The Cloud SQL remote MCP server now supports specialized endpoint URLs (toolsets) for <code>/readonly</code>, <code>/instance_manage</code>, and <code>/query_execution</code>. Specialized toolset URLs let you restrict the set of exposed MCP tools based on your security and workflow requirements.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/use-cloudsql-mcp#available-toolsets">Available toolsets</a>.</p>
<h3>Feature</h3>
<p>You can now use the <code>create_instance</code> tool in the Cloud SQL remote MCP server to provision free trial instances for testing and development by setting the <code>free_trial</code> parameter to <code>true</code>.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/use-cloudsql-mcp#create-free-trial">Create a free trial instance</a>.</p>
<h3>Feature</h3>
<p>When executing SQL queries using the <code>execute_sql</code> or <code>execute_sql_readonly</code> tool, setting the <code>sql_commenter_enabled</code> parameter to <code>true</code> automatically appends sqlcommenter tags (<code>mcp.tool</code>, <code>mcp.server</code>, <code>user.identity</code>, <code>mcp.client</code>) to SQL statements for enhanced database observability.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/mysql/use-cloudsql-mcp#sqlcommenter">sqlcommenter tags</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Feature</h3>
<p>The Cloud SQL remote MCP server now supports specialized endpoint URLs (toolsets) for <code>/readonly</code>, <code>/instance_manage</code>, and <code>/query_execution</code>. Specialized toolset URLs let you restrict the set of exposed MCP tools based on your security and workflow requirements.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/use-cloudsql-mcp#available-toolsets">Available toolsets</a>.</p>
<h3>Feature</h3>
<p>You can now use the <code>create_instance</code> tool in the Cloud SQL remote MCP server to provision free trial instances for testing and development by setting the <code>free_trial</code> parameter to <code>true</code>.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/use-cloudsql-mcp#create-free-trial">Create a free trial instance</a>.</p>
<h3>Feature</h3>
<p>When executing SQL queries using the <code>execute_sql</code> or <code>execute_sql_readonly</code> tool, setting the <code>sql_commenter_enabled</code> parameter to <code>true</code> automatically appends sqlcommenter tags (<code>mcp.tool</code>, <code>mcp.server</code>, <code>user.identity</code>, <code>mcp.client</code>) to SQL statements for enhanced database observability.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/use-cloudsql-mcp#sqlcommenter">sqlcommenter tags</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Feature</h3>
<p>You can now use the <code>update_user</code> tool in the Cloud SQL remote MCP server to update passwords for Cloud SQL for SQL Server database users.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/sqlserver/use-cloudsql-mcp#available-tools">Available tools</a>.</p>
<h3>Feature</h3>
<p>The Cloud SQL remote MCP server now supports specialized endpoint URLs (toolsets)
for <code>/readonly</code> and <code>/instance_manage</code>. Specialized toolset URLs let you restrict
the set of exposed MCP tools based on your security and workflow requirements.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/sqlserver/use-cloudsql-mcp#available-toolsets">Available toolsets</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>August 07, 2026</title>
    <id>tag:google.com,2016:cloud-sql-release-notes#August_07_2026</id>
    <updated>2026-08-07T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/sql/docs/release-notes#August_07_2026"/>
    <content type="html"><![CDATA[<h2 class="release-note-product-title">Cloud SQL for PostgreSQL</h2>
<h3>Change</h3>
<p>Newly created instances configured with <a href="https://docs.cloud.google.com/sql/docs/postgres/high-availability">high availability (HA)</a>
now have <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
enabled by default.</p>
<p>Cloud SQL for PostgreSQL instances running on PostgreSQL version 14.0 or later
send updates and metadata to Knowledge Catalog in near real-time.</p>
<p>You can either verify enablement or <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration#deactivate-dataplex-catalog">disable the feature</a>
using the Google Cloud console.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/sql/docs/postgres/dataplex-catalog-integration#near-real-time">Near real-time</a>.</p>
<h2 class="release-note-product-title">Cloud SQL for SQL Server</h2>
<h3>Change</h3>
<p>Newly created instances configured with <a href="https://docs.cloud.google.com/sql/docs/sqlserver/high-availability">high availability (HA)</a>
now have <a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration">Knowledge Catalog (formerly Dataplex Universal Catalog)</a>
enabled by default.</p>
<p>Cloud SQL for SQL Server instances send updates and metadata to Knowledge Catalog
to help support data discovery.</p>
<p>You can either verify enablement or <a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration#deactivate-dataplex-catalog">disable the feature</a>
using the Google Cloud console.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/sql/docs/sqlserver/dataplex-catalog-integration">Manage your Cloud SQL resources using Knowledge Catalog</a>.</p>
]]>
    </content>
  </entry>

</feed>
