Azure Database for PostgreSQL - Flexible Server versioning policy

APPLIES TO: Azure Database for PostgreSQL - Single Server Azure Database for PostgreSQL - Flexible Server

This page describes the Azure Database for PostgreSQL flexible server versioning policy, and is applicable to these deployment modes:

• Azure Database for PostgreSQL single server
• Azure Database for PostgreSQL flexible server

Supported PostgreSQL versions

Azure Database for PostgreSQL flexible server supports the following database versions.

Major version support

Each major version of PostgreSQL will be supported by Azure Database for PostgreSQL flexible server from the date on which Azure begins supporting the version until the version is retired by the PostgreSQL community. Refer to PostgreSQL community versioning policy.

Minor version support

Azure Database for PostgreSQL flexible server automatically performs minor version upgrades to the Azure preferred PostgreSQL version as part of periodic maintenance.

Major version retirement policy

The table below provides the retirement details for PostgreSQL major versions. The dates follow the PostgreSQL community versioning policy.

PostgreSQL 11 support

Azure is extending its support for PostgreSQL 11 within both the Azure Database for PostgreSQL Single Server and Azure Database for PostgreSQL Flexible Server platforms. This extended support timeline is designed to provide more time for users to plan and migrate to Azure Database for PostgreSQL flexible server for higher PostgreSQL versions.

PostgreSQL 12 support

PostgreSQL 12 is retiring on November 14, 2024, as per Azure's versioning policy, which aligns with the PostgreSQL community versioning policy. According to this policy, each major version is supported until it is retired by the community. However, Azure has extended support for PostgreSQL 11 until November 9, 2025, to give customers more time to plan and migrate from Azure Database for PostgreSQL Single Server to Flexible Server, as well as to higher PostgreSQL versions. This support extension is designed to provide a smoother transition for customers currently using PostgreSQL 11.

Single Server Support:

• Until March 28, 2025, users can continue to create and utilize PostgreSQL 11 servers on the Azure Database for PostgreSQL Single Server, except for creation through the Azure portal. It's important to note that other restrictions associated with retired PostgreSQL engines still apply.
• Azure will offer updates incorporating minor versions provided by the PostgreSQL community for PostgreSQL 11 servers until November 9, 2023.

Flexible Server Support

• Users can create and operate PostgreSQL 11 servers on Azure Database for PostgreSQL Flexible Server until November 9, 2025.
• Similar to the Single Server, updates with PostgreSQL community provided minor versions will be available for PostgreSQL 11 servers until November 9, 2023.
• From November 9, 2023, to November 9, 2025, while users can continue using and creating new instances of PostgreSQL 11 on the Flexible Server, they will be subject to the restrictions of other retired PostgreSQL engines.

This extension of Postgres 11 support is part of Azure's commitment to providing a seamless migration path and ensuring continued functionality for users.

Retired PostgreSQL engine versions not supported in Azure Database for PostgreSQL flexible server

You might continue to run the retired version in Azure Database for PostgreSQL flexible server. However, note the following restrictions after the retirement date for each PostgreSQL database version:

• As the community won't be releasing any further bug fixes or security fixes, Azure Database for PostgreSQL flexible server won't patch the retired database engine for any bugs or security issues, or otherwise take security measures regarding the retired database engine. You might experience security vulnerabilities or other issues as a result. However, Azure continues to perform periodic maintenance and patching for the host, OS, containers, and any other service-related components.
• If any support issue you might experience relates to the PostgreSQL engine itself, as the community no longer provides the patches, we might not be able to provide you with support. In such cases, you have to upgrade your database to one of the supported versions.
• You won't be able to create new database servers for the retired version. However, you'll be able to perform point-in-time recoveries and create read replicas for your existing servers.
• New service capabilities developed by Azure Database for PostgreSQL flexible server might only be available to supported database server versions.
• Uptime SLAs apply solely to Azure Database for PostgreSQL flexible server service-related issues and not to any downtime caused by database engine-related bugs.
• In the extreme event of a serious threat to the service caused by the PostgreSQL database engine vulnerability identified in, the retired database version, Azure might choose to stop your database server to secure the service. In such case, you are notified to upgrade the server before bringing the server online.
• The new extensions introduced for Azure Postgres Flexible Server will not be supported on the community retired postgres versions.

PostgreSQL version syntax

Before PostgreSQL version 10, the PostgreSQL versioning policy considered a major version upgrade to be an increase in the first or second number. For example, 9.5 to 9.6 was considered a major version upgrade. As of version 10, only a change in the first number is considered a major version upgrade. For example, 10.0 to 10.1 is a minor release upgrade. Version 10 to 11 is a major version upgrade.

Next steps

• See Azure Database for PostgreSQL single server supported versions.
• See Azure Database for PostgreSQL flexible server supported versions.