PostgreSQL 17 release delivers performance enhancements, improved JSON processing, and support for one-click in-place upgrades of existing servers.

What’s New

• General Availability of PostgreSQL 17 engine
  Benefit from the latest community innovations—improved vacuum performance, JSON functions enhancements, and dynamic logical replication—backed by Azure’s enterprise SLA.


• In-place Major Version Upgrade
  Upgrade your server “in place,” retaining your server name, connection strings, and configuration. No data migration, no downtime for read replicas, and minimal disruption.
  
  
  
  • One-click upgrade via Azure Portal
  
  
  • CLI support with az postgres flexible-server upgrade
  
  
  • Automated health checks and rollback safety
  
  
  
  


• Default Version
  PostgreSQL 17 is now the default for new server creations and major version upgrades.

PostgreSQL 17 Feature Highlights

Experience the next level of performance, scalability, and developer productivity with PostgreSQL 17:

• Advanced Vacuum Enhancements: Reduced maintenance overhead with smarter vacuum strategies and faster cleanup.


• JSON Processing Upgrades: New functions and optimizations for querying and transforming JSON data at scale.


• Dynamic Logical Replication: Simplify real-time data distribution with enhanced replication controls and improved throughput.


• Query Planner Improvements: Smarter join ordering and parallel plan enhancements for complex workloads.


• Security and Compliance : Strengthened encryption options and audit logging features to meet enterprise requirements.

Dive deeper into all the new features in the official PostgreSQL 17 release notes.

Why In-Place Upgrades Matter?

Traditional major-version upgrades often require provisioning a new server, copying data, and updating connection strings—steps that introduce complexity and risk. With in-place upgrades, you can:

1. Simplify operations: Keep your existing server endpoint and firewall rules.


2. Reduce downtime: Upgrade faster with built-in “stop, pg_upgrade, restart” workflow.


3. Maintain HA: For HA-enabled servers, we automatically disable HA, upgrade your primary, then recreate the replica—minimizing manual steps.

Did you know? Azure Database for PostgreSQL provides a 5-year standard support policy for each major engine version—so you’ll have long-term peace of mind as you plan and execute your upgrades.

How to Upgrade Today?

Portal

• Access your flexible server resource


• On the Overview page, in the toolbar, select Upgrade.


• Under Upgrade, select PostgreSQL 17 and click Upgrade


• In the Upgrade sidebar, in the PostgreSQL version to upgrade text box, verify the major version you want to upgrade to, that is “17”

CLI

Storage requirement: Ensure you have at least 10–20% free storage available to accommodate temporary files during pg_upgrade. Downtime advisory: Major version upgrades will incur downtime; the duration varies based on your database size and the number of tables it contains.

Conclusion

PostgreSQL 17 is now the default for new servers and ready for in-place upgrades on your existing flexible servers. Upgrade today to benefit from performance improvements, enhanced JSON support, and simplified major version upgrades. To learn more, read:

• PostgreSQL 17 Preview on Flexible Server (Sep 2024)


• Query Performance Improvements (Oct 2024)


• In-Place Upgrade Public Preview Recap (May 2025)


• Official PostgreSQL 17 Release Notes

Thank you for choosing Azure Database for PostgreSQL.