Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-version-policy below:

Version Policy - Azure Database for PostgreSQL

This article describes the Azure Database for PostgreSQL flexible server versioning policy.

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

A major version is a change in the first number of the version. For example, PostgreSQL 10 to PostgreSQL 11 is a major version upgrade. Major versions introduce new features and capabilities. They might include changes that require application code updates.

Azure Database for PostgreSQL supports each major PostgreSQL version from the date Azure begins offering support until the version reaches end of life (end of support) as defined by the PostgreSQL community. For details, see PostgreSQL community versioning policy.

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

Azure Database for PostgreSQL flexible server automatically upgrades minor versions to the Azure preferred PostgreSQL version during periodic maintenance.

To help you maintain secure and compliant workloads beyond community end-of-life (end of support), Azure is introducing Extended Support for Azure Database for PostgreSQL.

Extended Support gives you continued access to critical security updates and technical assistance. With Extended Support, you have time to plan and implement your upgrade strategy with confidence.

Extended support provides:

• Up to three extra years of support after standard support ends
• Security patches and critical bug fixes
• Technical support through Azure Support channels (per your existing plan)

Note

Extended Support doesn't include new feature releases, performance enhancements, or support for minor version upgrades.

Extended Support is ideal for customers who...

• Need more time to upgrade complex workloads.
• Require compliance and security coverage during upgrade planning.
• Depend on uninterrupted technical support for critical environments.

• Treat Extended Support as a temporary bridge, not a long-term solution.
• Start upgrade planning well before the end-of-life (end of support) date.
• Consider upgrading to newer versions such as PostgreSQL 15 or 16 for improved performance and support.

• Automatic Enrollment: PostgreSQL servers running unsupported versions are automatically enrolled in Extended Support on March 1, 2026.
• Opt-Out Option: You can opt out at any time by upgrading to a supported version.
• Grace Period: A one-month grace period applies. Billing begins on April 1, 2026.
• Pricing: Details will be published on this page before billing begins.

Q: What if I want to keep running without extended support? Can I opt out?

A: No.

Q: What happens if I continue running an unsupported PostgreSQL version on Azure after its community end of support?

A: Your server is automatically enrolled in Extended Support one month after the community end of support date (or on March 1, 2026, for versions 11, 12, and 13).

Q: Can I continue using my PostgreSQL instance without Extended Support?

A: Yes, but after the grace period, you're automatically enrolled in paid Extended Support unless you upgrade to a supported version. During the grace period, you assume full operational risk, and Microsoft support can't guarantee issue resolution.

Q: Can my applications break during a major version upgrade?

A: Azure provides preupgrade validation checks (PVC) to identify common issues such as extension compatibility and parameter conflicts. We recommend testing upgrades in nonproduction environments. Azure is also investing in Blue/Green deployments to enable near-zero-downtime upgrades.

Q: How do I know if my server is in Extended Support?

A: The Azure portal and CLI clearly indicate if a server is enrolled in Extended Support.

Q: Do I need to update Server Parameter Groups post major version upgrades?

A: Yes. Major PostgreSQL versions often introduce or deprecate configuration parameters. Create a new parameter group for the target version and adjust memory and performance settings as needed.

Q: Are PostgreSQL extensions automatically upgraded during a major version upgrade?

A: No. While Azure upgrades the database engine, noncore extensions (for example, pgvector, timescaledb) require manual updates. Use ALTER EXTENSION ... UPDATE or recreate unsupported extensions after the upgrade.

Q: How can I reduce downtime during a major upgrade?

A: To minimize downtime:

• Apply pending maintenance before the upgrade.
• Take a manual backup just before the upgrade to speed up snapshot creation.
• Schedule upgrades during low-traffic periods.
• Monitor replication lag and connections if using Blue/Green deployment.

Q: Where can I track which of my servers are nearing end of support?

A: Azure provides visibility through the portal.

Q: What support options are available during the Extended Support phase?

A: Servers in Extended Support can raise support cases for security-related issues only. Feature requests, performance tuning, and general bug fixes aren't supported for end of support versions. Improvements to existing features for end of support versions will not be backported.

Q: How will the period between November 13, 2025, and March 1, 2026, be handled for PostgreSQL version 13? Will support be continued during this time? How will it differ from the period before November 13, 2025?

A: According to the PostgreSQL community versioning policy, each major version is supported until retired by the community. Free Extended support from Azure will be provided through March 31, 2026. Customers are charged for Extended Support starting April 1. To ensure continued support and access to new features, upgrade to newer versions.

PostgreSQL 12 reaches end of life on November 14, 2024, in line with the PostgreSQL community versioning policy. According to this policy, the community supports each major version until retirement. Unlike PostgreSQL 11, which has extended support until November 9, 2025, Azure doesn't provide extended support for PostgreSQL 12 beyond March 1, 2026. Upgrade to newer versions to ensure continued support and access to new features.

Azure is extending support for PostgreSQL 11 on Azure Database for PostgreSQL flexible server. This extended support timeline gives you more time to upgrade to higher PostgreSQL versions. It facilitates a smooth transition for users currently relying on PostgreSQL 11.

• You can create and operate PostgreSQL 11 servers on Azure Database for PostgreSQL flexible Server until November 9, 2025, when Azure stops supporting PostgreSQL 11.
• From November 9, 2023, to November 9, 2025, you can continue using and creating new instances of PostgreSQL 11 on the flexible server, but there are restrictions for other retired PostgreSQL engines.

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

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

• When the community retires a PostgreSQL version, Azure Database for PostgreSQL flexible server stops applying bug or security patches to the database engine. This change might expose your server to security risks or other issues. However, Azure continues to maintain and patch the underlying host, operating system, containers, and related service components.

• If you experience a support issue that relates to the PostgreSQL engine itself, we might not be able to provide support because the community no longer provides the patches. In such cases, you need to upgrade your database to one of the supported versions.

• You can't create new servers by using a PostgreSQL version that is retired. However, you can 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 don't apply to any downtime caused by database engine-related bugs.

• In rare cases where a critical vulnerability in a retired PostgreSQL version poses a threat to the service, Azure might stop affected servers to protect the platform. In such cases, you're notified to upgrade the server before bringing the server online.

• New extensions introduced for Azure Database for PostgreSQL flexible server aren't supported on PostgreSQL versions that the community retired.

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.

• Supported versions of PostgreSQL in Azure Database for PostgreSQL flexible server

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4