AlloyDB Omni release notes

Stay organized with collections Save and categorize content based on your preferences.

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.

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

• AlloyDB Omni supports PostgreSQL version 16.3.
• Asynchronous I/O improves performance on systems with atomic writes for high concurrency Online Transaction Processing (OLTP) workloads. This feature is available in Preview.
• You can upgrade your AlloyDB Omni PostgreSQL 15-based containers to AlloyDB Omni PostgreSQL 16 using pg_upgrade. For more information, see Upgrade to AlloyDB Omni version 16.3.0 on a VM.
• AlloyDB Omni provides additional low-level logs (called "internal logs"), which are useful for debugging database issues. Production users are encouraged to enable this feature for greater observability. We recommend that you enable this feature to improve production observability.
• Active Directory integration lets you use your Active Directory Server to authenticate users for accessing your AlloyDB Omni 16.3.0 databases. This feature is available in Preview. For more information, see Integrate Active Directory with AlloyDB Omni.
• Multiple extensions are updated.
• Multiple GUCs have been updated or added.
• Security fixes for CVE-2024-7348 are implemented.
• Various bug fixes.

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

• AlloyDB Omni supports PostgreSQL version 15.7.
• AlloyDB Omni provides additional low-level logs (called internal logs), which are useful for debugging database issues. Production users are encouraged to enable this feature for greater observability. We recommend that you enable this feature to improve production observability.
• Multiple extensions are updated.
• Multiple GUCs have been updated or added.
• Security fixes for CVE-2024-7348 are implemented.
• Bug fixes.

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

• You can enable Active Directory integration on your Kubernetes-based AlloyDB Omni database cluster so that you can allow your existing Active Directory-based users to access your AlloyDB Omni database. This feature is available in Preview. For more information, see Integrate Active Directory with AlloyDB Omni on Kubernetes.
• You can create backups in any cloud or on-premises object storage systems that are compatible with the Amazon S3 API. For more information, see Create backups to S3-compatible storage (AlloyDB Omni 15.7.1 and 16.3.0).
• You can now access log files from sidecar containers.
• You can manually upgrade your AlloyDB Omni 15 database clusters to AlloyDB Omni 16.3.0 using pg_upgrade. For more information, see Migrate to the latest version of AlloyDB Omni on Kubernetes.
• Beginning with Kubernetes operator version 1.4.0, the 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.
• The PgBouncer connection pooler is generally available (GA). This release includes g-pgBouncer 1.4.0, which incorporates features and bug fixes from PgBouncer 1.24.0.
• You can configure the monitoring dashboard on your Grafana operator to visualize metrics using the monitoring endpoint of the Kubernetes operator.
• When the AlloyDB Omni Kubernetes Operator detects low disk space, the Kubernetes Operator reports a low disk space Critical Incident (CI) on the database cluster.
• AlloyDB Omni provides internal logs for debugging database issues. We recommend that you enable this feature to improve production observability. See "Enable internal logging" for AlloyDB Omni 15.7.1 and 16.3.0 for details.
• Disk cache metrics 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).
• Use 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.
• Various bug fixes and performance improvements.

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.

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.

AlloyDB 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.