Database version policies

Select a documentation version:

To plan database upgrades and keep your deployments running on supported PostgreSQL releases, review the support, retirement, and compatibility policies for AlloyDB Omni major and minor versions.

For information about AlloyDB for PostgreSQL version policies, see AlloyDB for PostgreSQL database version policies.

AlloyDB Omni version policies

Every version of AlloyDB Omni is compatible with a specific version of PostgreSQL, as detailed in Support policy.

Because AlloyDB Omni is software that you install and run yourself, you are responsible for regularly updating your AlloyDB Omni installation. Learn about the latest versions of AlloyDB Omni in the AlloyDB Omni release notes.

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 of updates to PostgreSQL support. These releases include bug fixes and security updates and are reflected in an incremental increase of the third number in the release version. For example, the 2 in 18.1.2 indicates an update to AlloyDB Omni.

Support policy

Google provides support for AlloyDB Omni versions based on the following timelines:

Version type Support period
Major versions Supported for 5 years from the initial release date, matching the community support lifecycle of the underlying PostgreSQL version.
Minor versions Supported for 1.5 years from their specific release date.

Major version support timeline

The general availability (GA) dates serve as the initial release dates for calculating the 5-year support window. The following table lists the GA dates and end-of-support dates for AlloyDB Omni PostgreSQL major versions:

PostgreSQL major version GA date End-of-support date
18 April 9, 2026 April 9, 2031
17 December 15, 2025 December 15, 2030
16 April 8, 2025 April 8, 2030
15 October 11, 2023 October 11, 2028

After a version exceeds its support period, it is considered retired. Google doesn't process support tickets for retired versions and recommends that you upgrade to a supported version to continue receiving assistance.

Supported PostgreSQL versions

For the Common Vulnerabilities and Exposures (CVEs) tracked across database releases, see the AlloyDB Omni security bulletin.

The following table lists the AlloyDB Omni minor versions, their compatible PostgreSQL versions, release dates, 1.5-year end-of-support dates, and support status:

AlloyDB Omni version PostgreSQL version Release date End-of-support date Status
18.4.0 18.4 October 13, 2026 April 13, 2028 Supported
18.3.0 18.3 July 15, 2026 January 15, 2028 Supported
18.1.0 18.1 April 9, 2026 October 9, 2027 Supported
17.10.0 17.10 October 13, 2026 April 13, 2028 Supported
17.9.0 17.9 July 15, 2026 January 15, 2028 Supported
17.7.0 17.7 April 9, 2026 October 9, 2027 Supported
17.5.0 17.5 December 15, 2025 June 15, 2027 Supported
16.14.0 16.14 October 13, 2026 April 13, 2028 Supported
16.13.0 16.13 July 15, 2026 January 15, 2028 Supported
16.11.0 16.11 April 9, 2026 October 9, 2027 Supported
16.9.0 16.9 December 15, 2025 June 15, 2027 Supported
16.8.0 16.8 July 23, 2025 January 23, 2027 Supported
16.3.0 16.3 April 8, 2025 October 8, 2026 Retired
15.18.0 15.18 October 13, 2026 April 13, 2028 Supported
15.17.0 15.17 July 15, 2026 January 15, 2028 Supported
15.15.0 15.15 April 9, 2026 October 9, 2027 Supported
15.13.0 15.13 December 15, 2025 June 15, 2027 Supported
15.12.0 15.12 July 23, 2025 January 23, 2027 Supported
15.7.1 15.7 April 8, 2025 October 8, 2026 Retired
15.7.0 15.7 November 8, 2024 May 8, 2026 Retired

Patch policy

To help maintain the security and stability of your environment, Google applies patches for critical bugs and vulnerabilities according to the following policy:

  • Google applies patches only to the latest minor version of each supported major version.
  • If you encounter an issue on an older minor version, you must upgrade to the latest available minor version of that major version to receive the fix.
  • Starting with AlloyDB Omni 16.9.0, 17.5.0, and 18.1.0, Google publishes database container images on both Red Hat Universal Base Image 9 (UBI 9) and Debian 12 (bookworm) tracks. UBI 9 images use the -ubi9 tag suffix for standalone container pulls. When a newer minor or patch version is released, Google marks superseded container image digests as deprecated. Always pull images that correspond to the latest supported release.
  • For information about CVEs addressed in AlloyDB Omni database container images, see AlloyDB Omni security bulletin.

Upgrade and compatibility

AlloyDB Omni version numbers use the format MAJOR_VERSION.MINOR_VERSION.OMNI_PATCH_VERSION to indicate the supported PostgreSQL version. The major and minor version numbers match the version of the underlying PostgreSQL engine, and the third number represents the AlloyDB Omni patch version.

The following table summarizes the upgrade and compatibility policies for AlloyDB Omni:

Policy category Description
Major version timing

Google aims to support new PostgreSQL major versions within eight months of the release of the first minor release, version x.1, of a new PostgreSQL major version.
Minor version timing Google aims to release support for new PostgreSQL minor versions every quarter. Because AlloyDB Omni is software that you install and run yourself, you must download and install the binaries that include upgraded PostgreSQL minor version compatibility.
Security updates Google aims to release fixes within one month of a PostgreSQL community security release.
Upgrade path
  • You can skip minor or patch versions during an upgrade if the version gap doesn't exceed the 1.5-year support period.
  • You can roll back only to the version that you used immediately before the upgrade.

Data protection

AlloyDB Omni doesn't perform automatic backups before an upgrade. You are responsible for taking a manual backup of your data before triggering an upgrade process.

What's next