AlloyDB for PostgreSQL release notes

This page documents production updates to AlloyDB for PostgreSQL. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.

November 08, 2024

AlloyDB Omni version 15.7.0 is generally available (GA). Version 15.7.0 includes the following features and changes:

  • AlloyDB Omni supports PostgreSQL version 15.7.

  • The alloydb_scann extension—previously named postgres_scann—is generally available (GA). For more information about storing vector embeddings, creating indexes, and tuning indexes to achieve faster query performance and better recall, see Work with vectors.

  • Support for Red Hat Enterprise Linux (RHEL) 8 is generally available (GA).

  • The AlloyDB Omni columnar engine is available in Preview on ARM.

  • Disk cache and columnar storage cache are available to improve AlloyDB Omni performance by accelerating data access for AlloyDB Omni in a container and on a Kubernetes cluster.

  • Security fixes for CVE-2023-50387 and CVE-2024-7348 have been implemented.

  • The AlloyDB Omni Reference documentation is available. This includes metrics, database flags, model endpoint management reference, and extensions documentation for AlloyDB Omni 15.7.0.

  • AlloyDB Omni supports the pg_ivm extension, which provides incremental view maintenance for materialized views.

  • Various bug fixes and performance improvements.

The AlloyDB Omni Kubernetes operator version 1.2.0 is generally available (GA). Version 1.2.0 includes the following new features:

  • The healthcheckPeriodSeconds parameter lets you specify the number of seconds to wait between health checks. For more information, see Adjust automatic failover trigger settings.

  • The following metrics help you monitor the performance of your database container. Each of these metrics is of type gauge. For more information, see Database container-level metrics.

    • alloydb_omni_memory_limit_byte shows the memory limit of a database container.

    • alloydb_omni_instance_postgresql_replication_state shows the state of each replica that's connected to the AlloyDB Omni primary node.

    • alloydb_omni_memory_used_byte shows the memory used by the database container in bytes.

  • An issue that caused a brief interruption to all database clusters when the following is true is fixed:

  • High availability is supported on a secondary database cluster after it's promoted. For more information, see Promote a secondary database cluster and Manage high availability in Kubernetes.

  • You can enable or disable model endpoint management through Kubernetes manifests. For more information, see Install AlloyDB Omni with AlloyDB AI.

  • You can configure when logs rotate using thresholds that are based on the size of the log files, the time since the log file last rotated, or both. For more information, see Configure AlloyDB Omni log rotation.

  • You can create a snapshot of the memory heap of AlloyDB Omni Kubernetes operator to help you analyze and debug its memory performance. For more information, see Analyze AlloyDB Omni Kubernetes operator memory heap usage.

In AlloyDB Omni versions 15.5.5 and earlier, parameterized view features were available in the alloydb_ai_nl extension. Starting in version 15.7.0, parameterized view features are available in the parameterized_views extension, which you must create before you use parameterized views. Also starting in version 15.7.0, the related function, google_exec_param_query, has been renamed to execute_parameterized_query and is available in the parameterized_views extension. For more information, see Query your database using natural language.

November 07, 2024

Since the google_ml_integration.enable_model_support flag is enabled by default, if you are using the google_ml_integration extension version 1.3, your ability to query Vertex AI models using the embedding() function might be impacted. Querying registered models using the google_ml.embedding() function remains unaffected.

To resolve the issue with using the embedding() function , upgrade the google_ml_integration extension version 1.3 to the latest version, 1.4.2. For more information, see how to upgrade the extension.

October 28, 2024

AlloyDB for PostgreSQL now supports in-place major version upgrade in Preview. You can upgrade your cluster that is compatible with PostgreSQL version 14 to 15. For more information, see Upgrade a database in-place major version.

October 23, 2024

Database server compatibility with PostgreSQL version 16 is generally available (GA). You can create AlloyDB clusters using PostgreSQL 16. Database Migration Service also supports homogeneous migrations from PostgreSQL to AlloyDB for PostgreSQL version 16.

October 10, 2024

AlloyDB lets you restart one or more nodes of a read pool. For more information, see Restart specific nodes of a read pool.

October 09, 2024

AlloyDB for PostgreSQL minor versions are upgraded to 15.7 and 14.12. For more information, see AlloyDB and AlloyDB Omni version policies.

October 02, 2024

The alloydb_scann extension (previously named postgres_scann) is generally available (GA) for the AlloyDB service in Google Cloud. For more information about storing vector embeddings, creating indexes, and tuning indexes to achieve faster query performance and better recall, see Work with vectors.

AlloyDB Omni is in Limited Availability on the Aiven Platform. Aiven provides managed AlloyDB Omni as a service on multiple public clouds. For more information, see Store your data on any major cloud.

September 30, 2024

AlloyDB outbound public IP connectivity on primary and secondary instances is generally available (GA).

September 25, 2024

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

September 18, 2024

The AlloyDB Omni operator is now available in Preview on Google Distributed Cloud (GDC) connected. For more information, see Install AlloyDB Omni on Kubernetes.

September 17, 2024

You can now add the predefined CMEK organization policy for your AlloyDB clusters and backups. This feature is generally available (GA).

September 16, 2024

The postgres_ann extension has been renamed to alloydb_scann. Before you upgrade to AlloyDB Omni Kubernetes operator version 1.1.1, you must drop any indexes created using the earlier postgres_ann version, then upgrade AlloyDB Omni, and then create the indexes again using the alloydb_scann extension.

Added a tutorial that shows you how to set up a connection from an application running in a Google Kubernetes Engine autopilot cluster to an AlloyDB instance.

AlloyDB Omni Kubernetes operator version 1.1.1 is now available. This patch fixes the following issues:

  • Fixed a regression for the AlloyDB Vertex AI integration.
  • Fixed a bug in which upgrading from version 1.0.0 to version 1.1.0 failed when using injected sidecars.
  • Fixed a bug in which backups weren't reestablished correctly across failovers when using the Commvault sidecar with high availability (HA) configurations.
  • Fixed a bug that caused a status to be incorrectly set by the load balancer, resulting in erroneous reports that the database cluster wasn't ready.

Upgrading to version 1.1.1 of the AlloyDB Omni Kubernetes operator might result in a brief interruption to all database clusters. No data loss is expected.

September 04, 2024

AlloyDB for PostgreSQL is now available in africa-south1 (Johannesburg) and in
me-central2 (Damman). For more information, see AlloyDB locations.

September 03, 2024

The extension pgvector is updated to version 0.7.2.

August 29, 2024

Query federation between BigQuery and AlloyDB is now generally available (GA). This feature lets you use BigQuery to query data stored in AlloyDB databases.

Database server compatibility with PostgreSQL version 16 is now available in Preview. You can create AlloyDB clusters with PostgreSQL 16 compatibility.

August 22, 2024

AlloyDB Omni now offers in-depth documentation that describes how to install and use AlloyDB Omni in virtual machine (VM) environments. The information in these documents is in addition to the AlloyDB Omni documentation that describes how to install and use AlloyDB Omni in VM and Kubernetes environments. For more information, see Get started with AlloyDB Omni on VMs.

The extension temporal_tables version 1.2.2 has been added to extensions supported by AlloyDB.

The following extensions are updated:

  • Updated pg_partman to version 4.7.4.
  • Updated pgtt to version 3.0.0.

August 16, 2024

August 14, 2024

The AlloyDB Omni Kubernetes Operator version 1.0.0 and later lets you schedule matching new database Pods to nodes to balance node distribution across the AlloyDB Omni cluster and help optimize performance.

August 08, 2024

Enhanced Query Insights and active queries are now available in Preview for read pool instances.

August 05, 2024

AlloyDB Omni version 15.5.5 is now generally available (GA). This version includes the following features and changes:

July 31, 2024

Gemini in Databases assistance in AlloyDB for PostgreSQL is now available in Preview for standard and enhanced query insights, system insights, index advisor, and active queries. You can use Gemini assistance to help you monitor and troubleshoot your AlloyDB resources. For more information, see Monitor and troubleshoot with Gemini assistance.

July 22, 2024

Support for public IP addresses with AlloyDB instances and creating organization policies with custom constraints is now generally available (GA).

July 16, 2024

Cross-region backup location is now generally available (GA).

July 10, 2024

July 09, 2024

The extension pgvector is updated to version 0.7.0.

Performing a switchover with zero data loss in cross-region replication setups, to test disaster recovery (DR) or to perform workload migration, is now generally available (GA).

July 01, 2024

The AlloyDB free trial clusters are now generally available (GA). These clusters let you test the majority of AlloyDB features for up to 30 days through a 8 vCPU basic primary instance along with an optional 8 vCPU read pool instance, and automatically scale storage up to 1TB.

June 25, 2024

AlloyDB Omni version 15.5.4 is generally available (GA). This version includes the following features and changes:

  • The simplified installation method for AlloyDB Omni is now generally available (GA). You can install and manage your AlloyDB Omni installation using common container-management tools such as Docker. For information on upgrading an existing AlloyDB Omni installation, see Migrate from an earlier version of AlloyDB Omni to the latest version.
  • AlloyDB Omni supports the Podman container tool on Red Hat Enterprise Linux (RHEL).
  • Support for Arm-based architectures is now available in Preview.
  • Various bug fixes and performance improvements.

June 14, 2024

The maintenance downtime for a basic instance has been improved to match that of an HA primary instance, ensuring both instance types experience minimal downtime of less than a second.

May 22, 2024

Query federation between BigQuery and AlloyDB is now available in Preview. This feature lets you use BigQuery to query data stored in AlloyDB databases.

May 10, 2024

Model endpoint management is now available in Preview for both AlloyDB and AlloyDB Omni. For more information, see Register and call remote AI models in AlloyDB or Register and call remote AI models in AlloyDB Omni.

Version 15.5.3 of the simplified installation method for AlloyDB Omni is now available in Preview. Updates include the following:

May 07, 2024

Private Service Connect is now generally available (GA). Private Service Connect lets you connect to an AlloyDB for PostgreSQL instance from multiple VPC networks belonging to different groups, teams, projects, or organizations.

AlloyDB Omni version 15.5.1 and later lets you add sidecar containers to your database cluster when you use the AlloyDB Omni Kubernetes Operator.

May 06, 2024

May 01, 2024

You can now set maintenance windows for your AlloyDB clusters. If you do, then AlloyDB schedules non-emergency maintenance events to begin only during the weekly period that you specify. You can also opt in to receive email notifications of upcoming maintenance events.

April 29, 2024

AlloyDB now supports up to 64 TiB storage per cluster in all locations. For more information about available locations, see AlloyDB locations.

April 12, 2024

AlloyDB Omni version 15.5.2 is now available. This version fixes the issue causing AlloyDB Omni running in Kubernetes to run out of memory and crash under some heavy workloads. To apply this fix to a database cluster running in Kubernetes, update its DBCluster manifest definition so that its databaseVersion value is "15.5.2".

April 09, 2024

The following Gemini in Databases features are now available in Public Preview:

  • Database Center: an AI-assisted dashboard that gives you one centralized view across your entire database fleet.
  • AlloyDB Studio (GA): lets authorized users interact directly with the SQL database and run SQL queries from the Google Cloud console to access and manipulate data.
  • Monitor active queries: monitor and troubleshoot the queries that are active in your database.
  • Index advisor: a fully managed index advisor that tracks the queries your database handles regularly.
  • Enhanced Query Insights: an assistive query performance diagnostics platform that lets you detect, troubleshoot, and prevent database and query performance problems in near real-time.
  • 4-week query metric retention in the Query Insights dashboard.
  • 5 new database insight recommendations.

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

AlloyDB Omni version 15.5.1 has the following AlloyDB AI features available in Preview:

April 08, 2024

You can preview a simplified installation method for AlloyDB Omni. This lets you install and run AlloyDB Omni on your environment using portable open-source tools, such as the docker command-line interface.

AlloyDB Omni version 15.5.1 is now available. This version includes the following features and changes:

The following issue was fixed on April 12, 2024.

Some heavy workloads might cause AlloyDB Omni running in Kubernetes to run out of memory and crash.

To mitigate this issue, make sure that transparent huge pages are enabled on your Kubernetes nodes:

  1. Follow the instructions on Configuring Transparent Huge Pages.

  2. On every node that you enable transparent huge pages on, run the following command:

    echo within_size > /sys/kernel/mm/transparent_hugepage/shmem_enabled

April 05, 2024

The following extensions are added to the extensions supported by AlloyDB.

  • autoinc
  • insert_username
  • moddatetime
  • pg_background
  • pg_squeeze
  • tcn

The extension pgvector is updated to version 0.6.0.

April 02, 2024

AlloyDB Studio is now generally available (GA). AlloyDB Studio includes an Explorer pane that integrates with an enhanced query editor, letting you browse, query, and modify your AlloyDB databases with this single interface. For more information, see Manage your data using AlloyDB Studio.

March 29, 2024

Fixed the issue causing AlloyDB clusters created using the Google Cloud CLI, the AlloyDB Admin API, or Terraform to have PostgreSQL 14 compatibility by default, instead of PostgreSQL 15 compatibility.

March 25, 2024

The following issue was fixed on March 29, 2024.

AlloyDB clusters created using the Google Cloud CLI, the AlloyDB Admin API, or Terraform have PostgreSQL 14 compatibility by default, instead of PostgreSQL 15 compatibility.

To mitigate this issue, take either one of the following steps:

  • Specify PostgreSQL version 15 when creating a cluster, instead of relying on the default value.
  • Use the Google Cloud console to create the cluster.

March 20, 2024

Updated the default major version of PostgreSQL compatibility for new AlloyDB clusters to PostgreSQL 15.

March 19, 2024

The Quotas documentation is updated to include additional guidance on setting the maximum number of concurrent connections for your database instance size.

March 15, 2024

The Back up and restore AlloyDB Omni documentation is updated to include pgBackRest, an open-source solution included with the AlloyDB Omni Docker container.

March 13, 2024

AlloyDB now supports continuous backup and recovery, and scheduled backups on secondary clusters. When you create a secondary cluster, any backup plans on the primary cluster are automatically copied to the new secondary cluster. For more information, see About cross-region replication.

March 12, 2024

AlloyDB Language Connectors are now generally available (GA). These language connectors are libraries that provide automated mutual TLS connections, IAM-based authorization, and Automated IAM Authentication when connecting to an AlloyDB instance. For more information about language connectors, see AlloyDB Language Connectors overview.

March 04, 2024

You can now use Key Access Justifications when working with external CMEK keys. This lets you view and manage external key access requests.

February 29, 2024

AlloyDB AI is now generally available (GA).

AlloyDB Omni version 15.5.0 is now available. This version includes the following features and changes:

  • When installing AlloyDB Omni using its command-line tool, you can now specify the TCP port that the instance accepts connections on.
  • Automated failover for highly available (HA) Kubernetes-based clusters is available in Preview.
  • The following extensions are updated:
    • Updated pg_cron to version 1.6.
    • Updated pg_repack to version 1.5.0.
    • Updated pgfincore to version 1.3.1.
    • Updated pglogical to version 2.4.4.
    • Updated pgvector to version 0.5.1.
  • The following extensions are now included:
    • Added autoinc version 1.0.
    • Added insert_username version 1.0.
    • Added moddatetime version 1.0.
    • Added tcn version 1.0.
  • Updated core PostgreSQL compatibility to version 15.5.
  • Applied security fix CVE-2024-0985 from PostgreSQL.
  • Various bug fixes and performance improvements.

The return value of the embedding() function of google_ml_integration has changed. The embedding() function now returns an array of REAL values, and not a VECTOR value. This allows you to install and use the extension without the requirement of installing pgvector as well.

If you wrote application code that uses embedding() during the Preview of AlloyDB AI, then you might need to update it to add explicit casting from the REAL[] data type to the VECTOR data type. For more information, see Work with vector embeddings.

A revised quickstart helps you install and run AlloyDB Omni on a Debian or Ubuntu system using a handful of commands.

February 28, 2024

AlloyDB now supports the use of Google Cloud tags on cluster and backup resources. Tags are key-value pairs you can apply to your resources for granular IAM permissions. To learn more, see Organize resources using tags. To use tags now, see Attach and manage tags on AlloyDB resources.

February 27, 2024

You can now use Automatic IAM Authentication with the AlloyDB Language Connectors (Preview) to connect to your cluster. For more information, see Connect using the AlloyDB Language Connectors.

February 20, 2024

You can now configure instances to use 128 vCPUs and 864 GB of RAM per node.

February 09, 2024

You can now use public IP with the AlloyDB Language Connectors (Preview) to connect to your cluster. For more information, see Connect using the AlloyDB Language Connectors.

February 06, 2024

AlloyDB for PostgreSQL is now available in europe-west10 (Berlin). For more information, see AlloyDB locations.

January 29, 2024

AlloyDB Public IP is now available in Preview. You can configure an AlloyDB instance to have a public IP address and accept connections from authorized external IP addresses.

Fixed the issue causing failed connections to certain AlloyDB instances when using Auth Proxy version 1.5.0.

January 25, 2024

AlloyDB Language Connectors are now available in Preview. These language connectors are libraries that provide automated mutual TLS connections, IAM-based authorization, and Automated IAM Authentication when connecting to an AlloyDB instance. For more information about language connectors, see AlloyDB Language Connectors overview.

January 24, 2024

AlloyDB support for Cloud regions in the events timeline is now Generally available.

January 22, 2024

AlloyDB now supports cross-project restoration. You can restore an AlloyDB cluster to a new cluster in a different Google Cloud Project.

January 19, 2024

AlloyDB database server compatibility with PostgreSQL version 15 is now generally available (GA). You can create or upgrade a cluster with PostgreSQL 15 compatibility.

December 20, 2023

AlloyDB Omni version 15.4.0 is now available. This version includes the following changes:

  • pgvector is updated to version 0.5.0
  • PostgreSQL is updated to version 15.4

The AlloyDB Omni Kubernetes Operator version 0.3.0 is now available in Preview, and includes bug fixes and improvements to the operator. For more information about upgrading AlloyDB using the Kubernetes operator, see Upgrade AlloyDB Omni.

December 18, 2023

Automated and continuous backups are now incremental backups. This allows AlloyDB to protect your data using smaller files rather than full backups, reducing your storage costs, and improving the backup speed.

December 15, 2023

AlloyDB for PostgreSQL now lets you monitor your AlloyDB instances using the AlloyDB System Insights dashboard or by using the Cloud Monitoring dashboard. You can also view metrics on the AlloyDB cluster Overview page.

December 14, 2023

AlloyDB now supports up to 64TiB storage per cluster in the following regions:

  • us-west1
  • us-central1
  • us-east1
  • us-east4
  • europe-west1
  • asia-east1
  • asia-southwest1

December 11, 2023

Terraform support for AlloyDB is now generally available (GA).

November 28, 2023

The AlloyDB columnar engine now supports columns with the array data type.

November 22, 2023

The following issue was fixed on January 29, 2024.

Version 1.5.0 of the AlloyDB Auth Proxy client might fail to connect to AlloyDB instances created before mid-November, 2023.

To mitigate this issue, take either one of the following steps:

  • Use version 1.4.1 of the AlloyDB Auth Proxy client. You can download this version by following the instructions on Download the Auth Proxy client, replacing 1.5.0 or latest in the commands with 1.4.1.

  • Update any database flag on the affected instance. We recommend using the Google Cloud console to set and then clear a flag that doesn't require the instance to restart, such as autovacuum. For a full list of flags, see Supported database flags.

November 15, 2023

IAM authentication for AlloyDB is generally available (GA).

You can now restrict an OAuth 2.0 access token so that it works only for AlloyDB authentication.

You can now configure the AlloyDB Auth Proxy to automatically authenticate IAM-based database logins. This works only with the IAM account that you use to run the proxy client.

AlloyDB Omni version 15.2.2 is available. This version resolves the previous version's issue with incremental backups, and contains various other bug fixes and improvements. For more information about upgrading AlloyDB Omni, see Upgrade AlloyDB Omni.

The AlloyDB Omni Kubernetes Operator version 0.2.0 is available in Preview. This update adds support for AlloyDB Omni version 15.2.2, and includes various bug fixes and improvements. For more information about upgrading AlloyDB using the Kubernetes operator, see Upgrade AlloyDB Omni.

November 08, 2023

The extension pgvector is updated to version 0.5.0.

The extension oracle_fdw is added to the extensions supported by AlloyDB. The extension provides a foreign data wrapper for accessing Oracle databases.

October 11, 2023

AlloyDB Omni is now generally available (GA).

In AlloyDB Omni version 15.2.1 and earlier, after a failover, when you promote a standby instance, incremental backups from the newly promoted instance might conflict with the existing backup files, and the backups might fail.

As a workaround, move the conflicting files into a separate directory.

The AlloyDB Omni Kubernetes Operator is now available in Preview. This extension to the Kubernetes API lets you deploy and manage AlloyDB Omni on a Kubernetes cluster.

September 28, 2023

AlloyDB secondary clusters now support read pool instances.

September 21, 2023

AlloyDB now offers basic instances, which are primary instances containing only one node, in one zone. Basic instances provide a lower-cost alternative to highly available instances, and are appropriate for use in non-production environments that don't require high availability.

Database server compatibility with PostgreSQL version 15 is now available in Preview. You can create a cluster with PostgreSQL 15 compatibility.

September 15, 2023

Maintenance operations on highly available primary instances now occur with less than one second of downtime for most workloads.

AlloyDB for PostgreSQL is now available in the following regions:

  • europe-west12 (Turin)
  • me-central1 (Doha)

For more information, see AlloyDB Locations.

September 13, 2023

AlloyDB now lets you use and manage data-encryption keys residing outside of Google Cloud using Cloud External Key Manager.

September 08, 2023

When creating an AlloyDB cluster, you can now specify an IP range for private services access. This is optional; if you do not specify an IP range, then AlloyDB selects one for you.

September 06, 2023

Updated the PostgreSQL-compatible server running on AlloyDB instances to version 14.7.

Updated the following extensions related to the PostGIS extension to version 3.2.3:

  • postgis
  • postgis_raster
  • postgis_sfcgal
  • postgis_tiger_geocoder
  • postgis_topology
  • address_standardizer
  • address_standardizer_data_us

The following extensions are updated:

  • Updated pg_hint_plan to version 1.4.1.
  • Updated pg_repack to version 1.4.8.
  • Updated pg_partman to version 4.7.3.
  • Updated postgresql-hll to version 2.17.
  • Updated pg_cron to version 1.5.
  • Updated pg_hint_plan to version 1.4.1.
  • Updated pg_repack to version 1.4.8.
  • Updated pg_partman to version 4.7.3.
  • Updated postgresql-hll to version 2.17.
  • Updated pg_cron to version 1.5.

August 29, 2023

AlloyDB AI, a suite of features for building generative AI applications, is now available with both AlloyDB and AlloyDB Omni. These features include the following:

  • The AlloyDB machine learning (ML) extension introduces an embedding SQL function. It lets you create vector embeddings from text using ML models. You can store these embeddings as vector data, and apply them as input to pgvector functions.

  • AlloyDB support for the pgvector extension brings performance enhancements for vector queries that run up to ten times faster than standard PostgreSQL, including an optimization that lets you create indexes of stored vector data using scalar quantization.

AlloyDB Omni version 15.2.0 is available in Preview. This version includes the following:

A separate Technology Preview edition of AlloyDB Omni is available. It lets you experiment with AlloyDB AI functionality using two included machine learning models trained on Google News text.

In AlloyDB Omni version 15.2.0, using the COPY function with the FREEZE option is disabled, due to a potential performance issue when loading large datasets.

August 22, 2023

You can now improve connection security by enforcing applications to connect to AlloyDB instances through AlloyDB connectors, such as the Auth Proxy.

You can now configure SSL enforcement mode to ensure that all database connections to an instance use SSL encryption.

August 16, 2023

Instance machine-type configuration has added an option for 96 vCPUs and 768 GB of RAM per node.

AlloyDB now offers committed use discounts (CUDs) that provide 25% or 52% discount on AlloyDB's compute resources in exchange for your commitment, and you can continuously use them for one- or three-year terms, respectively.

August 08, 2023

AlloyDB Omni version alloydb-omni-0.3.0-preview-postgresql-15.2 is available. This version introduces PostgreSQL 15, and applies various bug fixes and query performance improvements.

July 28, 2023

Cloud Asset Inventory support for AlloyDB is generally available (GA).

July 18, 2023

AlloyDB support for Data Residency is generally available (GA).

AlloyDB now supports setting up resource locations policies that can be used to constrain the location of new in-scope resources.

July 05, 2023

June 30, 2023

Vectorized join is available in Preview. Part of the AlloyDB columnar engine, vectorized join can improve the performance of joins by applying vectorized processing to qualifying queries.

Fault injection lets you test the resilience of a cluster's primary instance by simulating a sudden outage of its active node. This triggers the AlloyDB high availability feature that automatically promotes the instance's standby node to become the new active node.

June 27, 2023

IAM authentication for AlloyDB is available in Preview. You can add a role to Identity and Access Management (IAM) user or service accounts that lets them log into AlloyDB instances as database users.

The columnar engine now supports columns with the following data types:

  • boolean
  • bytea
  • enum
  • uuid

June 21, 2023

AlloyDB cross-region replication is generally available (GA).

June 20, 2023

The extension anon has been added to extensions supported by AlloyDB.

June 16, 2023

AlloyDB for PostgreSQL is now available in europe-west9 (Paris). For more information, see AlloyDB Locations.

June 12, 2023

You can increase your quotas by submitting a request in the Quotas page.

You can now manage the storage quota for clusters through the Quotas page.

June 05, 2023

AlloyDB for PostgreSQL is now available in the following regions:

  • us-east5 (Columbus)
  • us-south1 (Dallas)

For more information, see AlloyDB Locations.

June 01, 2023

Continuous backup and recovery is generally available (GA).

May 17, 2023

The AlloyDB FORCE_APPLY update policy is available in Preview. Use this policy to modify database flags and apply updates faster (within 1-2 minutes) to an instance.

May 12, 2023

The AlloyDB admin API now includes user-management methods. These let you use the gcloud command-line tool to manage the user roles of your AlloyDB clusters, in addition to the PostgreSQL functions already supported.

May 11, 2023

The storage per cluster limit has increased to 32 TiB.

May 10, 2023

The columnar engine now supports columns with json and jsonb data types.

May 09, 2023

AlloyDB for PostgreSQL is now available in the following regions:

  • asia-south2 (Delhi)
  • europe-southwest1 (Madrid)
  • europe-west4 (Netherlands)
  • europe-west8 (Milan)
  • me-west1 (Tel Aviv)
  • northamerica-northeast1 (Montreal)
  • northamerica-northeast2 (Toronto)
  • southamerica-east1 (Brazil)
  • southamerica-west1 (Santiago)

For more information, see AlloyDB Locations.

May 08, 2023

The AlloyDB index advisor is now generally available (GA).

The extensions pgtt and rdkit have been added to AlloyDB's supported extensions.

May 05, 2023

AlloyDB Omni version alloydb-omni-0.2.0-preview-postgresql-14.4 is available. This version reduces the memory requirement of AlloyDB Omni to 2 GB of RAM, and applies various bug fixes and query performance improvements.

April 24, 2023

Three metrics tracking node health are available in Preview. These can help you monitor the activity of individual read pool nodes, and investigate and troubleshoot issues with read pool queries.

April 06, 2023

AlloyDB for PostgreSQL is available in us-west2 (Los Angeles). For more information, see AlloyDB locations.

March 29, 2023

AlloyDB Omni is available in Preview. AlloyDB Omni is a downloadable edition of AlloyDB for PostgreSQL that lets you run a containerized AlloyDB database engine in your own computing environment.

March 06, 2023

Cloud Client libraries for the AlloyDB Admin API are in Preview. Supported languages include C++, C#, Go, and Java.

February 27, 2023

AlloyDB for PostgreSQL is available in the following regions:

  • asia-east1 (Taiwan)
  • asia-east2 (Hong Kong)
  • asia-northeast2 (Osaka)
  • asia-northeast3 (Seoul)
  • asia-south1 (Mumbai)
  • asia-southeast2 (Jakarta)
  • australia-southeast1 (Sydney)
  • australia-southeast2 (Melbourne)
  • europe-central2 (Warsaw)
  • europe-north1 (Finland)
  • europe-west2 (London)
  • europe-west6 (Zurich)
  • us-east1 (South Carolina)
  • us-east4 (Northern Virginia)
  • us-west1 (Oregon)
  • us-west3 (Salt Lake City)

For more information, see AlloyDB Locations.

February 16, 2023

Continuous backup and recovery is in Preview. This feature protects your clusters from data-loss events by letting you recover their data from any moment within a configurable window.

December 13, 2022

AlloyDB for PostgreSQL is generally available (GA).

December 12, 2022

The AlloyDB index advisor helps you optimize your databases by observing the queries your databases handle, and then recommending new indexes based on these observations.

December 08, 2022

AlloyDB cross-region replication replicates your primary cluster's data and resources. It makes the data and resources available in different regions, allowing disaster recovery in the event of an outage in the primary region.

December 01, 2022

The AlloyDB Clusters page of the Google Cloud console displays summary cards and a resource table that provide an overview on the overall health of your databases. This helps you monitor the real-time performance of your database fleet.

September 15, 2022

Datastream, Google Cloud's change data capture (CDC) and replication service, supports PostgreSQL for source databases. This means that you can use an AlloyDB database as a Datastream source.

Google Cloud Database Migration Service has added support for AlloyDB. This service can make it easier to migrate your existing PostgreSQL data and workloads to an AlloyDB cluster.

August 25, 2022

AlloyDB supports customer-managed encryption keys (CMEK), an alternative to its default Google-managed encryption. CMEK is especially useful for AlloyDB users who need to manage their own data encryption keys in order to satisfy specific compliance or regulatory requirements.

August 24, 2022

You can view which zones host a primary instance's active or standby VMs.

July 12, 2022

When creating a primary or read-pool instance, or scaling either one, you can choose a machine size as small as 2 vCPUs with 16 GB of RAM.

June 28, 2022

AlloyDB's Frequently asked questions page addresses common questions received by the AlloyDB support team during the product's public preview.

May 31, 2022

VPC Service Controls, a Cloud-wide feature that helps mitigate the risk of data exfiltration, is available with AlloyDB.

May 11, 2022

AlloyDB for PostgreSQL is available in Preview.