<?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:alloydb-release-notes</id>
  <title>AlloyDB for PostgreSQL - Release notes</title>
  <link rel="self" href="https://docs.cloud.google.com/feeds/alloydb-release-notes.xml"/>
  <author>
    <name>Google Cloud Platform</name>
  </author>
  <updated>2026-07-08T00:00:00-07:00</updated>

  <entry>
    <title>July 08, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#July_08_2026</id>
    <updated>2026-07-08T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#July_08_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>External search with AlloyDB now supports Apache <a href="https://docs.cloud.google.com/alloydb/docs/solr-search">Solr</a> in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>.
You can use the <a href="https://docs.cloud.google.com/alloydb/docs/reference/extensions#external_search_fdw"><code>external_search_fdw</code></a> extension to connect to a Solr cluster and query its data directly from your database.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>June 16, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#June_16_2026</id>
    <updated>2026-06-16T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#June_16_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB integration with Knowledge Catalog is now generally available (<a href="https://cloud.google.com/products#product-launch-stages">GA</a>).</p>
<p>This integration provides a unified metadata view to simplify data governance and analysis. It includes near real-time synchronization and expanded metadata details, like primary and foreign keys.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/knowledge-catalog-integration">Integrate AlloyDB with Knowledge Catalog</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>June 15, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#June_15_2026</id>
    <updated>2026-06-15T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#June_15_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>The Database Insights remote Model Context Protocol (MCP) server now supports
the following advanced query insights tools for AlloyDB for PostgreSQL:</p>
<ul>
<li><code>get_advanced_aggregated_query_stats</code></li>
<li><code>get_advanced_aggregated_wait_event_stats</code></li>
<li><code>get_advanced_time_series_query_stats</code></li>
<li><code>get_advanced_time_series_wait_event_stats</code></li>
<li><code>get_index_recommendations</code></li>
</ul>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/reference/mcp/databaseinsights/mcp/index">Database Insights remote MCP server</a>.</p>
<h3>Feature</h3>
<p>You can publish an <a href="https://docs.cloud.google.com/gemini/data-agents/conversational-analytics/alloydb/create-data-agents#publish-agent-gemini-enterprise">AlloyDB for PostgreSQL conversational analytics agent in
Gemini Enterprise</a>.
This feature is in
<a href="https://cloud.google.com/products/#product-launch-stages">Preview</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>June 02, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#June_02_2026</id>
    <updated>2026-06-02T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#June_02_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>You can now configure a cooldown period to determine when autoscaling occurs
for your read pool instances. For more information, see
<a href="https://docs.cloud.google.com/alloydb/docs/instance-read-pool-scale#autoscale-read-pool">Scale an instance</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>May 21, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#May_21_2026</id>
    <updated>2026-05-21T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#May_21_2026"/>
    <content type="html"><![CDATA[<h3>Fixed</h3>
<p>ChatGPT users are now able to list and use the AlloyDB toolset provided by the
AlloyDB remote MCP server.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>May 11, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#May_11_2026</id>
    <updated>2026-05-11T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#May_11_2026"/>
    <content type="html"><![CDATA[<h3>Announcement</h3>
<p>AlloyDB now offers extended support for clusters running major PostgreSQL versions that have reached their end-of-life (EOL) as defined by the PostgreSQL community. Extended support provides an additional three years of support after the end of regular support, giving you more time to plan and perform major version upgrades. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/extended-support">Extended support for AlloyDB for PostgreSQL</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 28, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_28_2026</id>
    <updated>2026-04-28T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_28_2026"/>
    <content type="html"><![CDATA[<h3>Change</h3>
<p>When the initial user or password is unspecified during cluster creation, a locked <a href="https://docs.cloud.google.com/alloydb/docs/database-users/overview#postgres-user"><code>postgres</code> role</a> with <code>null</code> password is created.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 22, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_22_2026</id>
    <updated>2026-04-22T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_22_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p><a href="https://docs.cloud.google.com/alloydb/docs/quick-start-migrations-guide">Database Migration Service quick-start migrations</a>
(in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>)
are now integrated into AlloyDB to provide a lightweight, continuous migration
flow. This feature automates setup for sources with private IPs in a VPC network,
including Cloud SQL for PostgreSQL and self-managed databases on Compute Engine.</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/database-migration/docs/about-quick-start-migrations">Quick-start migrations overview</a>
in the Database Migration Service documentation.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 21, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_21_2026</id>
    <updated>2026-04-21T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_21_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>The integration between AlloyDB for PostgreSQL and Knowledge Catalog (in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>) is now enabled by default for all new AlloyDB clusters.</p>
<p>This integration provides a unified view of your metadata to simplify data governance and analysis. Recent enhancements feature near real-time synchronization, with updates reflecting in Knowledge Catalog within minutes, as well as expanded metadata details that now include Primary Keys and Foreign Keys.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/knowledge-catalog-integration">Integrate AlloyDB for PostgreSQL with Knowledge Catalog</a>.</p>
<h3>Feature</h3>
<p>You can now use the AlloyDB columnar engine to act as a read-optimized,
in-memory cache for HNSW indexes. This
increases the number of queries per second (QPS) that your database can handle
for vector search workloads. This feature is available in
<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/accelerate-with-ce">Accelerate vector search with the
columnar engine</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 20, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_20_2026</id>
    <updated>2026-04-20T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_20_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>You can now use the <a href="https://docs.cloud.google.com/alloydb/docs/reference/mcp/databaseinsights/mcp/index">Database Insights remote MCP server</a> to analyze AlloyDB's performance and system metrics. This feature is in <a href="https://cloud.google.com/products#product-launch-stages">GA</a>.</p>
<h3>Feature</h3>
<p>The AlloyDB remote MCP server—available through the global endpoint—is now generally
available (<a href="https://cloud.google.com/products#product-launch-stages">GA</a>)
and includes support for the following:</p>
<ul>
<li>Read-only execute SQL.</li>
<li>Tools to help you update your instance, export and import data, create a
backup, and restore your cluster.</li>
<li>Public IP.</li>
<li>Private Service Connect endpoint automation.</li>
</ul>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/use-alloydb-mcp">Use the AlloyDB remote MCP server</a>.</p>
<h3>Issue</h3>
<p>ChatGPT users aren't able to list or use the AlloyDB toolset provided
by the AlloyDB remote MCP server.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 17, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_17_2026</id>
    <updated>2026-04-17T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_17_2026"/>
    <content type="html"><![CDATA[<h3>Issue</h3>
<p>When querying your Elasticsearch data using
<a href="https://docs.cloud.google.com/alloydb/docs/elastic-search#sql-query">standard SQL queries</a> and specifying an
<code>OFFSET</code>, if the <code>OFFSET</code> gets pushed down, it gets applied twice. For example,
if your SQL query contains <code>OFFSET 5</code>, AlloyDB tries
to push the <code>OFFSET</code> down. Then, AlloyDB applies the
<code>OFFSET</code> again when the results are returned.</p>
<h3>Feature</h3>
<p>External search with AlloyDB now supports Elasticsearch in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>.</p>
<p>With this update, you can use the <code>external_search_fdw</code> extension to connect to Elasticsearch and perform hybrid searches within AlloyDB. This integration allows you to combine the capabilities of AlloyDB with Elasticsearch for advanced search scenarios. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/elastic-search">Access Elasticsearch data from AlloyDB</a>.</p>
<h3>Announcement</h3>
<p>The following AlloyDB AI function capabilities are available in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>:</p>
<ul>
<li>You can now use AI function acceleration and the new <code>AI Function Apply</code> node to run faster queries with AI functions. This feature optimizes the execution of SQL queries that use the <code>ai.if</code> and <code>ai.rank</code> functions in PostgreSQL 17. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/accelerate-ai-queries">Accelerate performance for queries with AI functions</a>.</li>
<li>You can now use optimized AI functions to accelerate your AI queries while reducing operational costs. By training a smaller, faster proxy model on a sample
of your data, AlloyDB can process most AI queries locally and only fall back to a remote LLM when necessary. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/accelerate-queries-optimized-functions">Accelerate queries using optimized functions</a>.</li>
<li><p>You can now use the sentiment analysis and summarization functions. These functions let you process and analyze unstructured data directly in your database:</p>
<ul>
<li><code>ai.analyze_sentiment</code>: classifies the emotional tone of text as positive, negative, or neutral, helping you analyze real-time customer feedback from thousands of raw, unstructured product reviews.</li>
<li><code>ai.summarize</code>: condenses lengthy text into its essential information. Use this to extract key decisions and action items from sources like meeting transcripts or technical documentation.</li>
<li><code>ai.agg_summarize</code>: an aggregate function that processes multiple rows in a column to generate a single, unified summary for a group. For instance, you can summarize all reviews for a specific seller using a <code>GROUP BY</code> clause.</li>
</ul>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/evaluate-sentiment">Evaluate sentiment</a> and <a href="https://docs.cloud.google.com/alloydb/docs/ai/summarize-content">Summarize content</a>.</p></li>
</ul>
]]>
    </content>
  </entry>

  <entry>
    <title>April 16, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_16_2026</id>
    <updated>2026-04-16T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_16_2026"/>
    <content type="html"><![CDATA[<h3>Announcement</h3>
<p>The following vector search improvements are now available in
<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>:</p>
<ul>
<li>AlloyDB now supports Vector assist. Vector assist is an
AlloyDB extension that simplifies the deployment and management of your
AlloyDB vector workloads. It helps you set up production-ready vector search
capabilities, such as embedding generation, query optimization, and index
creation for vector types like HNSW. For more information about vector
assist, how it works, and its limitations, see
<a href="https://docs.cloud.google.com/alloydb/docs/ai/vector-assist-overview">Vector assist overview</a>.</li>
<li>You can now defer ScaNN index creation on an empty table or a table with
insufficient rows until the table has sufficient data. For more information,
see <a href="https://docs.cloud.google.com/alloydb/docs/ai/create-scann-index#deferred-index-creation-for-empty-tables-insufficient-rows">Create a ScaNN index</a>.</li>
<li>The <code>alloydb_scann</code> extension now supports four-level tree indexes,
providing support for tables with up to 10 billion vector rows. For more
information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/create-scann-index#create-scann-index-manual">Four-level ScaNN tree
indexes</a>.</li>
</ul>
<h3>Feature</h3>
<p>Adaptive filtering from inline filtering to pre-filtering is now generally
available (<a href="https://cloud.google.com/products#product-launch-stages">GA</a>).
With AlloyDB AI, you can use adaptive filtering to optimize filtered
vector searches. This feature enables the query optimizer to use cost-based
analysis to dynamically choose the most efficient filtering strategy—either
inline filtering or pre-filtering—based on real-time data distributions. This
improves filtered vector search performance without requiring manual tuning or
intervention. Note that the feature adaptive filtering from pre-filtering to inline
filtering is still in
<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>.</p>
<p>For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/adaptive-filtering">Understand adaptive filtering in AlloyDB AI</a>.</p>
<h3>Announcement</h3>
<p>The <code>alloydb_scann</code> extension is updated to include the following
vector search improvements. These features are generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>):</p>
<ul>
<li>By default, new ScaNN vector index builds are automatically tuned.
Manually-tuned indexes can be converted to automatically-tuned indexes. For
more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/create-scann-index">Create a ScaNN
index</a>.</li>
<li>You can now automatically maintain your ScaNN vector indexes. AlloyDB
incrementally manages your index such that when your dataset grows, AlloyDB
updates centroids and splits large outlier partitions to provide better QPS
and search results. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/maintain-vector-indexes#maintain-index-automatically">Maintain indexes
automatically</a>.</li>
</ul>
]]>
    </content>
  </entry>

  <entry>
    <title>April 15, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_15_2026</id>
    <updated>2026-04-15T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_15_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>The AlloyDB for PostgreSQL index advisor is enabled by default. It provides vector
search index recommendations for Scalable Nearest Neighbors (ScaNN) indexes. For
more information, see <a href="https://docs.cloud.google.com/alloydb/docs/use-index-advisor">Use the index advisor</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 14, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_14_2026</id>
    <updated>2026-04-14T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_14_2026"/>
    <content type="html"><![CDATA[<h3>Breaking</h3>
<p>As of April 10, 2026, you can create, run, and edit
<a href="https://docs.cloud.google.com/cloud-assist/investigations">Gemini Cloud Assist investigations</a>
only if you have a <a href="https://cloud.google.com/support/premium">Premium Support contract</a>.
You can use Gemini Cloud Assist investigations to
<a href="https://docs.cloud.google.com/alloydb/docs/monitor-troubleshoot-with-ai">monitor and troubleshoot your AlloyDB for PostgreSQL instance with AI assistance</a>.</p>
<p>If you ran an investigation prior to April 10, 2026, then the results of the
investigation continue to be available to you in the Google Cloud console.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 06, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_06_2026</id>
    <updated>2026-04-06T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_06_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>The QueryData tool lets you to query the data in your database using
conversational language and build data agents. For more information, see
<a href="https://docs.cloud.google.com/alloydb/docs/ai/data-agent-overview">QueryData tool
overview</a>.
This feature is available in
(<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>).</p>
<p>The preview release increases the accuracy of SQL generation with value search queries which match values and their context within a database. Value search queries trigger automatically. QueryData also adds support for Parameterized secure views (PSVs) to help secure applications that use natural language queries. For more information, see <a href="https://cloud.google.com/alloydb/docs/ai/secure-app-data-parameterized-secure-views">Secure and control access to application data using parameterized secure views</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 03, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_03_2026</id>
    <updated>2026-04-03T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_03_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>The <a href="https://docs.cloud.google.com/sdk/gcloud/reference/beta/alloydb/connect"><code>gcloud beta alloydb connect</code></a>
command is now available in
<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>. This command
provides a simplified way to connect securely to AlloyDB
instances by using the AlloyDB Auth Proxy and <code>psql</code>. For more information,
see <a href="https://docs.cloud.google.com/alloydb/docs/connect-gcloud">Connect using gcloud CLI</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>April 02, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#April_02_2026</id>
    <updated>2026-04-02T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#April_02_2026"/>
    <content type="html"><![CDATA[<h3>Change</h3>
<p>You can now enable <a href="https://docs.cloud.google.com/alloydb/docs/cross-region-replication/work-with-cross-region-replication#secondary-cluster-instance">Advanced Query Insights on primary
clusters</a>
which have secondary clusters configured. Advanced Query Insights is not supported on secondary
clusters. If you perform a switchover, you must re-enable Advanced Query
Insights on the new primary cluster.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 31, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_31_2026</id>
    <updated>2026-03-31T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_31_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>Hot standby enhances the AlloyDB high availability (HA) architecture to improve
failover times and to ensure consistent performance after failover. AlloyDB
continuously replicates transactions to the standby node to keep caches warm
and to ensure that the node is ready to take over quickly during a failover.
This feature is generally available (<a href="https://cloud.google.com/products#product-launch-stages">GA</a>) in PostgreSQL 18 and is automatically
enabled for all new instances. For more information, see the
<a href="https://docs.cloud.google.com/alloydb/docs/high-availability">AlloyDB high availability overview</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 30, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_30_2026</id>
    <updated>2026-03-30T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_30_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB now offers conversational analytics, which lets users query their
operational data using natural language. This feature is powered by the
<a href="https://docs.cloud.google.com/gemini/data-agents/conversational-analytics-api/overview">Conversational Analytics API</a>,
which can help you translate complex human dialog into precise database queries
to provide actionable insights. This feature is in
<a href="https://docs.cloud.google.com/products#product-launch-stages">Preview</a>.
For more information, see <a href="https://docs.cloud.google.com/gemini/data-agents/conversational-analytics/alloydb">Conversational analytics for AlloyDB overview</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 25, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_25_2026</id>
    <updated>2026-03-25T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_25_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>Database server compatibility with PostgreSQL version 18 is now generally
available (<a href="https://cloud.google.com/products#product-launch-stages">GA</a>):</p>
<ul>
<li>You can <a href="https://docs.cloud.google.com/alloydb/docs/cluster-create#procedure">create AlloyDB clusters</a>
with PostgreSQL 18 compatibility.</li>
<li>You can <a href="https://docs.cloud.google.com/alloydb/docs/upgrade-db-inplace-major-version">upgrade</a> existing
AlloyDB clusters running PostgreSQL major versions 14, 15, 16, or 17 to
PostgreSQL major version 18 with one click.</li>
<li>You can use Database Migration Service to
<a href="https://docs.cloud.google.com/database-migration/docs/postgresql-to-alloydb/migration-src-and-dest">migrate databases to AlloyDB</a>.</li>
</ul>
<h3>Feature</h3>
<p>The following AlloyDB AI features are available in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>:</p>
<ul>
<li><p>You can now use the <code>ai.hybrid_search()</code> function, which fuses results from
each search type into a single list using the Reciprocal Rank Fusion (RRF)
algorithm. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/run-hybrid-vector-similarity-search">Run hybrid vector similarity search</a>.</p></li>
<li><p>AlloyDB supports the <code>rum</code> extension for complex full-text search
operations. The <code>rum</code> extension extends standard GIN indexes by storing
positional information directly in the index. This enables faster phrase
searches and relevance ranking without needing to access the table data. For
more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/create-rum-index">Create and manage a RUM index</a>.</p></li>
</ul>
<h3>Change</h3>
<p>When no major version is specified, AlloyDB for PostgreSQL now defaults to
<a href="https://docs.cloud.google.com/alloydb/docs/db-version-policies#support-table">PostgreSQL major version 17</a>
for new clusters.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 20, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_20_2026</id>
    <updated>2026-03-20T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_20_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB lets you monitor node-level metrics in Google Cloud console
and Metrics Explorer to provide detailed troubleshooting guidance for read
pools and to identify nodes causing performance regressions. For more
information, see <a href="https://docs.cloud.google.com/alloydb/docs/reference/system-insights-metrics">System insights metrics reference</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 16, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_16_2026</id>
    <updated>2026-03-16T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_16_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB now supports the 2 vCPU C4A machine type (<code>c4a-highmem-2-lssd</code>),
which is powered by Google Axion, Google's custom Arm-based processor.
This expansion provides a smaller entry point and more flexibility for
scaling your production workloads using Axion-based instances. For more information,
see <a href="https://docs.cloud.google.com/alloydb/docs/choose-machine-type">Choose an AlloyDB machine type</a>.</p>
<h3>Feature</h3>
<p>AlloyDB enhanced backups are generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>).
You can now select the Enhanced tier during cluster creation, manage your
project-level backups with tiered tabs, and delete an enhanced backup. For more
information, see
<a href="https://docs.cloud.google.com/alloydb/docs/backup/manage-enhanced-backups">Manage enhanced backups</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 05, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_05_2026</id>
    <updated>2026-03-05T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_05_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB enhanced backups are generally available
(<a href="https://cloud.google.com/products#product-launch-stages">GA</a>).
You can now select the Enhanced tier during cluster creation, manage your
project-level backups with tiered tabs, and delete an enhanced backup. For more
information, see
<a href="https://docs.cloud.google.com/alloydb/docs/backup/manage-enhanced-backups">Manage enhanced backups</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 03, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#March_03_2026</id>
    <updated>2026-03-03T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#March_03_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>The following AlloyDB AI features are now generally available (<a href="https://cloud.google.com/products#product-launch-stages">GA</a>):</p>
<ul>
<li><p><a href="https://docs.cloud.google.com/alloydb/docs/ai/generate-manage-auto-embeddings-for-tables">Auto vector embeddings</a> provide a scalable, automated solution for managing the lifecycle of vector embeddings for large-scale datasets, eliminating the need for manual reindexing or custom scripts. This feature keeps embeddings in sync with transactional data and now supports incremental refresh in <code>manual</code> mode, ensuring that embeddings are only generated for new or updated rows. Additionally, you can perform incremental table refreshes or migration up to 130x faster than traditional row-by-row processing using <code>bulk</code> mode, improving efficiency for semantic search and Retrieval Augmented Generation (RAG).</p></li>
<li><p><a href="https://docs.cloud.google.com/alloydb/docs/ai/ai-query-engine-landing">AI functions</a> integrate LLMs like Gemini to bring 'world knowledge' to your AlloyDB data and incorporate advanced semantic search and ranking capabilities directly into your SQL workflows. This feature includes out-of-the-box functions for filtering (<code>ai.if</code>), semantic ranking (<code>ai.rank</code>), generation (<code>ai.generate</code>), and forecasting (<code>ai.forecast</code>).</p></li>
<li><p>Experience higher performance in AlloyDB AI by utilizing array-based AI functions. You can perform batch processing of natural language prompts directly within your SQL queries, significantly improving efficiency for large-scale AI operations. For more information, see <a href="https://docs.cloud.google.com/alloydb/docs/ai/evaluate-semantic-queries-ai-operators">Perform intelligent SQL queries using AI functions</a>.</p></li>
</ul>
]]>
    </content>
  </entry>

  <entry>
    <title>February 23, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#February_23_2026</id>
    <updated>2026-02-23T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#February_23_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>Gemini Cloud Assist investigation capabilities are now supported in
AlloyDB (<a href="https://cloud.google.com/products/#product-launch-stages">Preview</a>).</p>
<p>For more information, see
<a href="https://docs.cloud.google.com/alloydb/docs/troubleshoot/slow-queries-ai">Troubleshoot slow queries with AI assistance</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>February 19, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#February_19_2026</id>
    <updated>2026-02-19T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#February_19_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB now integrates with Database Center to provide prioritized health
monitoring in the Google Cloud console. This integration highlights critical
and high-priority risks, offering one-click navigation to recommended fixes and
system insights for quick resolution. For more information, see
<a href="https://docs.cloud.google.com/alloydb/docs/monitor-health-clusters-instances">Monitor the health of your AlloyDB clusters and instances</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>February 17, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#February_17_2026</id>
    <updated>2026-02-17T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#February_17_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>AlloyDB <a href="https://docs.cloud.google.com/alloydb/docs/optimize-database-performance-compare-snapshots">performance snapshot and reports</a> now support read pool instance nodes, providing deeper observability into read operations and replica-specific performance issues.</p>
<h3>Announcement</h3>
<p>New best practices are available for securing generative AI agents using Model
Context Protocol (MCP) with Google Cloud databases. This guide covers key
security measures like least privilege, native database controls, and secure
agent design to help you build safer AI applications. For more information, see
<a href="https://docs.cloud.google.com/alloydb/docs/ai/secure-agent-interactions-mcp">Best practices for securing agent interactions with Model Context Protocol</a>.</p>
<h3>Feature</h3>
<p>You can now make AI function calls in bulk rather than row-by-row, which lets you
scale your intelligent workflows faster with new support for array-based
processing. For more information, see
<a href="https://docs.cloud.google.com/alloydb/docs/ai/evaluate-semantic-queries-ai-operators">Perform intelligent SQL queries using AI functions</a>.</p>
<p>This feature is in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>.</p>
<h3>Feature</h3>
<p>You can now use the <a href="https://docs.cloud.google.com/alloydb/docs/ai/use-alloydb-mcp">AlloyDB remote MCP server</a>.
The AlloyDB remote MCP server lets you interact easily with AlloyDB clusters
from LLMs, AI applications, and AI-enabled development platforms.</p>
<p>This feature is in <a href="https://cloud.google.com/products#product-launch-stages">Preview</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>February 09, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#February_09_2026</id>
    <updated>2026-02-09T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#February_09_2026"/>
    <content type="html"><![CDATA[<h3>Fixed</h3>
<p>We are announcing the release of support for the AlloyDB language connectors and
Auth Proxy with <a href="https://docs.cloud.google.com/alloydb/docs/connect-iam#automatic">Auto IAM Authentication</a>
and managed connection pooling. This feature and the fix for the issue from
below is available starting with maintenance version 20260107.02_05. Clusters
with a maintenance window that may not have received this release can use
<a href="https://docs.cloud.google.com/alloydb/docs/self-service-maintenance">self-service maintenance</a>
to perform a maintenance update.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>February 05, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#February_05_2026</id>
    <updated>2026-02-05T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#February_05_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p><a href="https://cloud.google.com/alloydb/docs/columnar-engine/add-frequent-expressions">Virtual columns for
expressions</a>
is a feature of the columnar engine in
<a href="https://cloud.google.com/products#product-launch-stages">Preview</a> that
significantly improves query performance and reduces CPU consumption. It caches
the results of frequently used expressions, which is especially beneficial for
analytical workloads on large datasets. This feature is supported for PostgreSQL
version 16 and higher.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>January 27, 2026</title>
    <id>tag:google.com,2016:alloydb-release-notes#January_27_2026</id>
    <updated>2026-01-27T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/alloydb/docs/release-notes#January_27_2026"/>
    <content type="html"><![CDATA[<h3>Feature</h3>
<p>Database server compatibility with PostgreSQL version 18 is now available for
preview (<a href="https://cloud.google.com/products#product-launch-stages">Preview</a>).
You can
<a href="https://cloud.google.com/alloydb/docs/cluster-create#procedure">create AlloyDB clusters</a>
with PostgreSQL 18 compatibility.</p>
]]>
    </content>
  </entry>

</feed>
