This page describes database version support policies for AlloyDB Omni.
Every version of AlloyDB Omni has compatibility with a specific version of PostgreSQL, as detailed in Major version compatibility release policy.
Because AlloyDB Omni is software that you install and run yourself, you are also responsible for regularly updating your AlloyDB Omni installation as needed. The availability of new versions of AlloyDB Omni is announced on AlloyDB Omni release notes.
Major and minor version support
AlloyDB Omni supports compatibility with the following PostgreSQL database versions:
| PostgreSQL version | AlloyDB Omni version |
|---|---|
| 16.3 | 16.3.0 |
| 15.7 | 15.7.0 15.7.1 |
| 15.5 | 15.5.0 15.5.1 15.5.2 15.5.5 |
| 15.4 | 15.4.0 |
| 15.2 | 15.2.2 |
Major version support timeline
The following table lists the general availability (GA) dates of AlloyDB support for PostgreSQL major versions.
| PostgreSQL major version | GA date |
|---|---|
| 16 | April 7, 2025 |
| 15 | October 11, 2023 |
Major version compatibility release policy
We aim to offer timely support for AlloyDB Omni compatibility
with new PostgreSQL major versions, specifically within eight months of the
PostgreSQL release numbered MAJOR_VERSION.1.
The version number of an AlloyDB Omni release reflects its version of PostgreSQL support. AlloyDB Omni version numbers use the following format:
MAJOR_VERSION.MINOR_VERSION.OMNI_VERSION
For example, AlloyDB Omni version 15.4.2 represents version 2 of the AlloyDB Omni release that supports compatibility with PostgreSQL version 15.4.
We plan to support AlloyDB Omni compatibility with any one major PostgreSQL version for at least as long as the PostgreSQL community supports that same major version—that is, no less than five years.
These are general guidelines. The actual release times for any new version may differ.
Major version deprecation plan
Google uses the PostgreSQL community's end-of-life schedule when planning the end of AlloyDB Omni support for compatibility with any PostgreSQL major version.
When Google intends to end compatibility support for a specific major version of PostgreSQL, we provide the following to project owners:
- End-of-support notices, sent at least 12 months ahead of time.
- Tools and documentation to minimize upgrade disruption, as needed.
Minor version support
AlloyDB Omni aims to release compatibility support for a new minor PostgreSQL version every quarter. These updates include bug fixes and security fixes. The schedule may vary depending on the need for additional bug fixes.
For AlloyDB Omni, you must download and install the binaries that include upgraded PostgreSQL minor-version compatibility.
Some AlloyDB Omni releases are updates to AlloyDB Omni itself, independent from updates to PostgreSQL support. These releases include bug fixes and security updates, and are reflected by an increment to the last part of the release version number.
AlloyDB Omni CLI version
The AlloyDB Omni CLI uses a MAJOR.MINOR versioning scheme
that indicates only the version of the CLI itself. Its version numbers and its
versioning schedule exist independently from AlloyDB Omni.
The major version of the AlloyDB Omni CLI is increased only upon the introduction of changes that are backwards-incompatible with the previous release of the CLI.
Security updates
When the PostgreSQL community releases minor versions with security fixes, the AlloyDB Omni security team reviews them for the criticality and impact.
For AlloyDB Omni, we release a new binary that has the fix with the new minor version within a month of the PostgreSQL community release.