Feature Direct Iceberg access in AlloyDB for PostgreSQL is available for PostgreSQL 18 and later (in Preview). This feature lets you query Apache Iceberg tables in Cloud Storage or Lakehouse runtime catalog and accelerate analytical queries using the AlloyDB columnar engine. For more information, see Access Iceberg data from AlloyDB. Feature Syncing data from BigQuery into AlloyDB is generally ava…
Change AlloyDB for PostgreSQL now defaults to PostgreSQL major version 18 for new clusters.
Feature You can now tune SQL queries using AI. Available starting with version 1.6.2 of the google_ml_integration extension, the ai.tune_sql function uses an LLM along with query execution plans, schemas, and runtime stats to recommend query optimizations. The function identifies performance bottlenecks and provides recommendations for query rewrites, indexes, statistics collection, Grand Unified…
Fixed For AlloyDB clusters compatible with PostgreSQL 18 or later, an instance restart is no longer required when you enable or edit Advanced Query Insights settings, including changing the query length or enabling active query analysis. For clusters compatible with PostgreSQL 17 or earlier, saving changes still requires an instance restart. For more information, see Use Advanced Query Insights an…
Feature AlloyDB AI adds pre-registered support for the following Gemini models in version 1.6.5 and later of the google_ml_integration extension: gemini-3.1-flash-lite gemini-3.5-flash gemini-3.5-flash-lite gemini-3.6-flash gemini-3.7-flash gemini-3.8-flash gemini-4-argon Version 1.6.5 of the google_ml_integration extension sets gemini-3.5-flash-lite as the default Gemini model and removes the gem…
Announcement The following AlloyDB AI and vector search features and improvements are generally available (GA): The alloydb_scann extension supports four-level tree (4LT) ScaNN vector indexes on PostgreSQL 17 and later, providing support for tables with up to 10 billion vector rows. For more information, see Four-level ScaNN tree indexes. 4LT ScaNN vector indexes support automatic index maintenanc…
Announcement The following AlloyDB AI functions and improvements are available in Preview: The ai.extract function lets you extract structured data from unstructured text directly within your database queries without needing external extraction pipelines. For more information, see Extract structured data. The ai.classify function lets you categorize unstructured text into predefined labels directl…
Feature Lakehouse federation in AlloyDB is generally available (GA). This feature lets you query live data in BigQuery directly from AlloyDB using the bigquery_fdw extension without moving or duplicating the data. For more information, see Access to real-time data in BigQuery overview and Configure access to real-time data in BigQuery.
Feature You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes. This feature is generally available (GA). It accelerates vector search performance and increases queries per second (QPS) for vector workloads. For more information, see Accelerate queries with the Columnar Engine.
Feature You can now monitor the status, throughput, and backlog of the audit logging pipeline for your AlloyDB for PostgreSQL instances and nodes using Cloud Monitoring. For more information, see Monitor audit log pipeline status.
Feature AlloyDB real-time data access to BigQuery (in Preview) now offers limit pushdown and runtime projects: Limit pushdown: when you query foreign tables, some LIMIT and OFFSET clauses are automatically pushed down to BigQuery, reducing network transfer and improving query response times. For more information, see Access to real-time data in BigQuery overview. Runtime projects: you can specify…
Fixed AlloyDB now provides more accurate memory usage estimation, and it prevents out-of-memory (OOM) errors when you build a ScaNN four-level tree index. This feature is in Preview. This update improves the stability of index builds by enforcing memory limits and improving memory estimation under constrained conditions. For more information, see Create a ScaNN index.
Feature You can now use the Model Context Protocol (MCP) Toolbox for Databases to access AlloyDB observability features and advanced query insights directly in your IDE.
Feature You can now sync tables from BigQuery into your AlloyDB instance, either as a one-time operation or on a periodic schedule. This feature (in Preview) lets you enable operational analytics that benefit from low-latency, transactional access to your data lake. For more information, see Sync BigQuery data to AlloyDB. Feature AlloyDB integration with BigQuery lets you connect your operational…
Feature AlloyDB now supports Best Matching 25 (BM25) indexes for full-text search in Preview. You can use the pg_textsearch extension to create BM25 indexes and optimize probabilistic ranking of full-text search. This feature is supported on AlloyDB instances running PostgreSQL 17 or 18. For more information, see Create and manage a BM25 index.
Feature Note: IAM group authentication is available in Preview for new AlloyDB clusters. To enable this feature on an existing cluster, contact your Google Cloud account team. IAM group authentication for AlloyDB is available in Preview for new clusters running PostgreSQL 15 and later. This feature simplifies database user management by allowing access management at the group level, where group me…
Feature External search with AlloyDB now supports OpenSearch in Preview. You can use the external_search_fdw extension to connect to an OpenSearch cluster and query its data directly from your database.
Feature Transparent query forwarding is now available in Preview for clusters compatible with PostgreSQL 17 and 18. With this feature, the primary node in a cluster intercepts read-only queries and selectively forwards them to read pool instances while maintaining read-your-writes consistency. For more information, see Optimize resources and isolate read queries with transparent query forwarding.
Feature External search with AlloyDB now supports Apache Solr in Preview. You can use the external_search_fdw extension to connect to a Solr cluster and query its data directly from your database.
Feature AlloyDB integration with Knowledge Catalog is now generally available (GA). 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. For more information, see Integrate AlloyDB with Knowledge Catalog.
Feature The Database Insights remote Model Context Protocol (MCP) server now supports the following advanced query insights tools for AlloyDB for PostgreSQL: get_advanced_aggregated_query_stats get_advanced_aggregated_wait_event_stats get_advanced_time_series_query_stats get_advanced_time_series_wait_event_stats get_index_recommendations For more information, see Database Insights remote MCP serve…
Feature You can now configure a cooldown period to determine when autoscaling occurs for your read pool instances. For more information, see Scale an instance.
Fixed ChatGPT users are now able to list and use the AlloyDB toolset provided by the AlloyDB remote MCP server.
Announcement 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 Extended support for AlloyDB for P…
Change When the initial user or password is unspecified during cluster creation, a locked postgres role with null password is created.
Feature Database Migration Service quick-start migrations (in Preview) 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. For more information, see Quick-start migrations overview in the Database Migration Ser…
Feature The integration between AlloyDB for PostgreSQL and Knowledge Catalog (in Preview) is now enabled by default for all new AlloyDB clusters. 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 deta…
Feature You can now use the Database Insights remote MCP server to analyze AlloyDB's performance and system metrics. This feature is in GA. Feature The AlloyDB remote MCP server—available through the global endpoint—is now generally available (GA) and includes support for the following: Read-only execute SQL. Tools to help you update your instance, export and import data, create a backup, and rest…
Issue When querying your Elasticsearch data using standard SQL queries and specifying an OFFSET, if the OFFSET gets pushed down, it gets applied twice. For example, if your SQL query contains OFFSET 5, AlloyDB tries to push the OFFSET down. Then, AlloyDB applies the OFFSET again when the results are returned. Feature External search with AlloyDB now supports Elasticsearch in Preview. With this upd…
Announcement The following vector search improvements are now available in Preview: 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.…