AlloyDB Omni version 16.8.0 is generally available (GA). Version 16.8.0 includes the following features and changes:
pg_squeeze extension
that addresses table bloat and improves data locality.libaio.AlloyDB Omni version 15.12.0 is generally available (GA). Version 15.12.0 includes the following features and changes:
pg_squeeze extension
that addresses table bloat and improves data locality.The AlloyDB Omni Kubernetes operator version 1.5.0 is generally available (GA) and includes the following features and bug fixes:
You can install the operator using the Operator Lifecycle Manager (OLM) for Kubernetes and OpenShift environments. See "Install the AlloyDB Omni operator" for AlloyDB Omni 15.12.0 and 16.8.0 for details.
Low downtime, minor version upgrades for a database cluster in a high availability setup are available in Preview. For more information, see "Perform a minor database version upgrade for AlloyDB Omni on Kubernetes" in the documentation for AlloyDB Omni 15.12.0 and 16.8.0.
Active Directory authentication integration on your Kubernetes-based AlloyDB Omni database cluster is generally available (GA). For more information, see Integrate Active Directory with AlloyDB Omni on Kubernetes.
Active Directory group-based authorization on your Kubernetes-based AlloyDB Omni database cluster is available in Preview. For more information, see Integrate Active Directory group support on Kubernetes.
You can configure backups to be taken directly from a standby Kubernetes cluster in a high availability (HA) setup to offload backup operations from your primary instance. See "Backup and restore in Kubernetes" for AlloyDB Omni 15.12.0 and 16.8.0 for details.
The operator fully automatically replicates replication slots for cross-data-center replication to work with primary database clusters that have high availability (HA) enabled. You still need to make sure you have reliable and low latency network connectivity between the primary and secondary data centers, which is crucial for cross-data-center replication to function effectively. For more information, see "Work with cross-data-center replication" for AlloyDB Omni 15.12.0 and 16.8.0.
AlloyDB Omni Kubernetes images are now built on Red Hat's Universal Base Image (UBI) 9. For more information, see "Install AlloyDB Omni on Kubernetes" for AlloyDB Omni 15.12.0 and 16.8.0.
AlloyDB AI requires AlloyDB Omni version 15.5.5 or later.
When upgrading your AlloyDB Omni database clusters, be aware of specific upgrade paths and prerequisites depending on your current controlPlaneAgentsVersion and environment:
If your database cluster's controlPlaneAgentsVersion is 1.0.0, you must first upgrade to 1.1.1 before you upgrade to 1.5.0 or higher. You can directly upgrade database clusters with controlPlaneAgentsVersion 1.1.0 or later to 1.5.0.
If you use an OpenShift database cluster that runs controlPlaneAgentsVersion 1.4.1 or earlier, you must run prerequisite steps before updating to 1.5.0. For more information, see "Update OpenShift database clusters from version 1.4.1 or earlier" for AlloyDB Omni 15.12.0 and 16.8.0.
The AlloyDB Omni Kubernetes operator version 1.4.1 is generally available (GA) and includes the following bug fixes:
wal_keep_size value. For more information, see Work with cross-data-center replication. This fix requires database version 15.7.1 or later.AlloyDB Omni version 16.3.0 with Red Hat Universal Base Image (UBI) as a base image is generally available (GA). The image is RedHat certified and can also be accessed from the Red Hat Ecosystem Catalog. Version UBI 16.3.0 includes third-party extensions, including PostGIS and Orafce, which you can install on RPM-based Linux distributions. For more information about using UBI in AlloyDB Omni, see Install AlloyDB Omni on a VM.
]]>AlloyDB Omni is in General 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.
The alloydb_scann extension is updated to include the following vector search improvements. These features are generally available (GA):
Inline filtering enables the execution of vector search and filter evaluation through the combined use of vector and secondary indexes. For more information, see "Inline filtering" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can let AlloyDB automatically create multiple parallel workers during index creation when the dataset grows, leading to faster build times. For more information, see "Build indexes in parallel" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
A distribution histogram is available in the pg_stat_ann_indexes view, which helps you understand the distribution of vectors between partitions of your ScaNN index. For more information, including recommendations about tuning the distributionpercentile metric, see "Tuning metrics" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.
You can use a query recall evaluator to find the recall for a vector query for a given configuration, and to tune your parameters to achieve the desired vector query recall results for different vector indexes. For more information, see "Measure vector query recall" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.
The alloydb_scann extension is updated to include the following vector search improvements in (Preview):
You can enable auto-maintenance for your ScaNN index and let incrementally manage the index such that when your dataset grows, AlloyDB splits large outlier partitions, and tries to provide better QPS and search results. For more information, see "Maintain indexes automatically" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
Adaptive filtering for ScaNN significantly improves the speed of filtered vector searches. Adaptive filtering automatically selects the most efficient filtering method at runtime. For more information, see "Filtered vector search" and "Adaptive filtering" in the documentation for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can enable index auto maintenance and adaptive inline filtering together using the scann.enable_preview_features Grand Unified Configuration (GUC) parameters. For more information, see "AlloyDB flags" for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
If you use mutating admission webhooks in your Kubernetes cluster, you might experience issues when you create database clusters and the webhooks conflict with the AlloyDB Omni Kubernetes Operator. Examples of mutating admission webhooks include LimitRanger and DefaultTolerationSecond. When the conflict occurs, the database pod repeatedly switches between running and terminating. To work around this issue, disable these webhooks where you run your AlloyDB Omni database cluster.
Action required: You can access Kubernetes operator 1.4.0 high availability (HA) improvements for automatic setup, failover, and healing capabilities starting with AlloyDB Omni 15.7.1 and later. To access these features, see "Migrate to the latest version of AlloyDB Omni on Kubernetes" for AlloyDB Omni 15.7.1 and 16.3.0.
AlloyDB Omni version 16.3.0 is generally available (GA). Version 16.3.0 includes the following features and changes:
pg_upgrade. For more information, see Upgrade to AlloyDB Omni version 16.3.0 on a VM.AlloyDB Omni version 15.7.1 is generally available (GA). Version 15.7.1 includes the following features and changes:
The PostgreSQL Audit Extension (pgaudit) logging fix In AlloyDB Omni 15.7.0, which enables the pgAudit extension together with the PostgreSQL logging_collector parameter, might have resulted in audit logs loss. This issue is fixed in AlloyDB Omni versions 15.7.1 and 16.3.0.
The AlloyDB Omni Kubernetes operator version 1.4.0 is generally available (GA). Version 1.4.0 includes the following new features and changes:
pg_upgrade. For more information, see Migrate to the latest version of AlloyDB Omni on Kubernetes.alloydb_omni_instance_postgresql_wait_time_second_total metric is renamed to alloydb_omni_instance_postgresql_wait_time_us_total to reflect the correct unit of the metric value. If you are not already using microseconds (us) for your metric unit, your queries and dashboard calculations need to change to reflect the correct unit of this metric: seconds -> us. For more information, see Upgrade your AlloyDB Omni Kubernetes operator to version 1.4.0.alloydb_omni_database_postgresql_chill_cache_get_entry_calls_total and alloydb_omni_database_postgresql_chill_cache_num_hits_total are exposed when you enable disk cache on AlloyDB Omni versions 15.7.1 and 16.3.0. These metrics are database container-level metrics. For more information, see AlloyDB Omni metrics (15.7.1 and 16.3.0).alloydb_omni_instance_postgresql_version to get the current PostgreSQL major version. For more information, see "Database container-level metrics" for AlloyDB Omni 15.7.1 and 16.3.0.The Kubernetes 1.4.0 DBCluster might have a status of DBClusterReady even though its endpoint, which allows clients to connect, is not yet ready.
When the ScaNN index creation updates the reltuples statistics of a heap table, performance might be degraded for queries involving that table. For information to mitigate the issue, see Analyze your indexed table.
The AlloyDB Omni Kubernetes operator version 1.3.0 is generally available (GA). Version 1.3.0 includes the following new features and changes:
The Kubernetes operator 1.3.0 supports connection pooling (Preview).
You can put the database in maintenance mode to make a maintenance update or repair a pod.
You can create replication slots and users for logical replication via the Operator API from your database instance to subscribed applications.
This release of the Kubernetes operator adds support for kube-state-metrics so that you can use Prometheus or a Prometheus-compatible scraper to consume and display custom resource metrics like DBCluster Backup, and DBInstance. For more information, see Monitor AlloyDB Omni Kubernetes operator custom resources.
When you create a new database cluster, this version of the Kubernetes operator creates read-only (RO) and read-write (RW) load balancers concurrently, which reduces the time that it takes for the database cluster to be ready for connections and queries.
Configurable log rotation has a default retention time of seven days, and each archived file is individually compressed using Gzip. For more information, see Configure AlloyDB Omni log rotation.
Various bug fixes and performance improvements.
Model endpoint management is generally available (GA) for both AlloyDB and AlloyDB Omni. You can use sample templates to register model endpoints. For more information, see Register and call remote AI models in AlloyDB or Register and call remote AI models in AlloyDB Omni.
]]>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:
You're upgrading the AlloyDB Omni Kubernetes operator version 1.1.1 to a newer version.
You're using the AlloyDB Omni database version 15.5.5 or later.
AlloyDB AI is not enabled.
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.
The extension pg_ivm version 1.9 has been added to extensions supported by AlloyDB Omni.
The following extensions are updated:
google_ml_integration from 1.3 to 1.4.2pg_partman from 4.7.4 to 5.0.1pglogical from 2.4.4 to 2.4.5pgtt from 3.0.0 to 4.0.0vector is updated from 0.7.0 to 0.7.4AlloyDB for PostgreSQL minor versions are upgraded to 15.7 and 14.12. For more information, see AlloyDB and AlloyDB Omni version policies.
]]>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.
]]>The AlloyDB Omni operator is now available in Preview on Google Distributed Cloud (GDC) connected. For more information, see Install AlloyDB Omni on Kubernetes.
]]>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:
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.
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.
]]>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:
pg_partman to version 4.7.4.pgtt to version 3.0.0.The AlloyDB Omni Kubernetes Operator version 1.1.0 lets you configure a load balancer using annotations.
]]>AlloyDB Omni version 15.5.5 is now generally available (GA). This version includes the following features and changes:
The AlloyDB Omni Kubernetes Operator version 1.1.0 is generally available (GA) and it includes the following new features:
The postgres_ann extension is renamed to alloydb_scann. Before you upgrade AlloyDB Omni, you must drop any indexes created using the older postgres_ann version, then upgrade AlloyDB Omni, and then create the indexes again using the alloydb_scann extension.
Various bug fixes.
AlloyDB Omni version 15.5.4 is generally available (GA). This version includes the following features and changes: