This monthly recap highlights enhancements across maintenance, upgrade readiness, monitoring, scalability, storage, authentication, and lifecycle support. Key updates include adaptive autovacuum, pre-upgrade validation, new PgBouncer monitoring, PostgreSQL 18 support for Elastic Clusters, Terraform support for Premium SSD v2, and Entra ID token-refresh libraries.
Table of Contents
- Adaptive autovacuum
- Pre-upgrade Validation Checks now generally available, including CLI support
- New PgBouncer metric: Total client connections (Preview)
- August 2026 PostgreSQL minor version update
- Elastic Clusters now available for PG18
- New and Improved Troubleshooting Guides for Azure Postgres
- Azure Advisor Enhancements
- Terraform support for Premium SSDv2
- Entra-ID token refresh libraries for .NET, JavaScript, and Python: GA
- Extended support for Azure PostgreSQL
Adaptive autovacuum
Adaptive autovacuum enhances PostgreSQL built-in autovacuum process in Azure Database for PostgreSQL flexible server, adjusting vacuum activity to changing workload conditions to maintain database health by cleaning dead tuples, reducing table and index bloat, and lowering the risk of transaction ID wraparound without requiring administrators to tune static autovacuum settings.
The feature uses workload and table-level signals to adapt autovacuum behavior, balancing maintenance work with application performance. It is especially valuable for databases with variable update and delete patterns, where fixed thresholds and scale factors can cause vacuuming to run too late or too aggressively.
Learn more: Adaptive Autovacuum in Azure Database for PostgreSQL flexible server
Pre-upgrade Validation Checks now generally available, including CLI support
Pre-upgrade Validation Checks for Azure Database for PostgreSQL Flexible Server are now generally available through the Azure portal and CLI. Assess your server’s readiness for a major version upgrade without performing the upgrade, identify compatibility issues and upgrade blockers, and review actionable remediation guidance before your planned upgrade window. This helps teams address prerequisites earlier and make upgrade planning more predictable.
With Azure CLI 2.89.0 or later, use the --validate-only parameter with az postgres flexible-server upgrade to incorporate readiness checks into scripts and operational workflows. In the Azure portal, select Validate only in the Upgrade pane to review results and download a CSV report. Resolve any blocking issues, rerun validation, and initiate the major version upgrade separately when ready.
Learn more: Run pre-upgrade validation checks
New PgBouncer metric: Total client connections (Preview)
The new Total client connections (Preview) metric gives Azure Database for PostgreSQL Flexible Server customers a server-level view of client connections currently tracked by PgBouncer - including active, idle, waiting, and authenticating connections. Unlike backend connection metrics, it captures client-side connection usage, helping you understand how close your application is to the configured pgbouncer.max_client_conn limit and investigate connection pressure.
Available as client_connections_total, the metric complements existing active and waiting client connection metrics to support capacity planning and troubleshooting.
To collect PgBouncer metrics, enable pgbouncer.enabled and metrics.pgbouncer_diagnostics, then view the metric in Azure Monitor where the preview is available. The value represents the current connection count, not a cumulative total over time.
Documentation: Monitor PgBouncer metrics
August 2026 PostgreSQL minor version update
Azure Database for PostgreSQL Flexible Server now supports PostgreSQL minor versions 18.6, 17.11, 16.15, 15.19, and 14.24 as part of the August 2026 release. These updates keep workloads current within their existing PostgreSQL major version. The August maintenance release also includes security fixes, hardening improvements, and service reliability fixes.
Existing servers receive the update through scheduled maintenance. Deployment proceeds region by region, so availability can vary and the global rollout can take up a few weeks. Monitor your server’s maintenance notifications to understand when the update will be applied.
Learn more: Supported versions of PostgreSQL
Elastic Clusters now available for PG18
Powered by Citus 14.0, Elastic Clusters bring Postgres 18 capabilities to a fully managed, distributed Postgres experience on Azure.
Build new applications or modernize existing ones with the performance, reliability, and developer improvements of PostgreSQL 18—combined with the flexible scaling and operational simplicity of Azure Postgres Elastic Clusters.
You can explore PostgreSQL 18 performance improvements, new SQL capabilities, and developer-focused features while scaling distributed workloads across tables, shards, and nodes.
New and Improved Troubleshooting Guides for Azure Postgres
Updated troubleshooting guidance is now available for Azure Database for PostgreSQL flexible server. You can use the expanded documentation to diagnose high CPU, memory, IOPS, temporary file usage, and autovacuum issues, helping you identify root causes and resolve performance problems more efficiently.
The update provides end-to-end investigation workflows for the built-in troubleshooting guides and explains how to correlate Azure Monitor metrics, Query Store statistics, session data, and server logs. You can learn how to configure the required telemetry, identify the query, session, wait events, or configuration behind an issue, and apply targeted mitigations before deciding to scale your server.
Our modernized troubleshooting guides deliver richer performance insights, intuitive controls, and clearer recommendations to help users diagnose issues faster, optimize configurations confidently, and improve performance across CPU, memory, storage, and autovacuum workloads.
Azure Advisor Enhancements
Advisor now features three new active monitors for your Azure Database for PostgreSQL flexible server covering your Storage, Connectivity, and Compute configurations. These recommendations ensure you can take advantage of storage auto-grow, enable the built-in connection pooler, and upgrade legacy performance SKUs to the current configurations when needed.
Terraform support for Premium SSDv2
You can now use Terraform to deploy Azure Database for PostgreSQL Flexible Server with Premium SSD v2 storage. Premium SSD v2 gives you more control over storage performance by letting you independently configure capacity, IOPS, and throughput. This can be especially useful for workloads that need higher storage performance without increasing disk size.
Support is now available in the azurerm_postgresql_flexible_server resource starting with AzureRM provider version 5.4.0. You can configure Premium SSD v2 by setting storage_type to PremiumV2_LRS, along with the desired IOPS and throughput values.
resource "azurerm_postgresql_flexible_server" "example" {
name = "example-postgresql"
resource_group_name = azurerm_resource_group.example.name
location = azurerm_resource_group.example.location
sku_name = "GP_Standard_D4s_v5"
storage_type = "PremiumV2_LRS"
storage_mb = 131072
storage_iops = 3000
storage_throughput = 125
}
Premium SSD v2 supports up to 64 TiB capacity, 80,000 IOPS and 1,200 MB/s throughput, depending on your storage and compute configuration, and is available with General Purpose and Memory Optimized compute tiers.
For more details, see the Premium SSD v2 documentation and the AzureRM provider update.
Entra-ID token refresh libraries for .NET, JavaScript, and Python: GA
We’re announcing General Availability of Entra ID token refresh libraries for .NET, JavaScript, and Python to simplify how applications authenticate with Azure Database for PostgreSQL using Entra ID. When using Entra ID–based authentication, access tokens are short-lived and need to be refreshed periodically. This often requires additional logic in the application to handle expiration, retries, and reconnection scenarios. These new libraries take care of that complexity by automatically refreshing tokens behind the scenes, so applications can maintain uninterrupted database connections without custom token management.
With built-in support for token renewal, these libraries help:
- Reduce the need for manual token refresh logic in your application code
- Improve reliability for long-running or connection-pooled workloads
- Simplify adoption of Entra ID authentication across different language stacks
Whether you're building new applications or migrating existing ones to use Entra ID, these libraries make it easier to integrate secure, passwordless authentication while keeping connection handling straightforward.
Extended support for Azure PostgreSQL
As PostgreSQL versions approach end of standard support, planning ahead remains the best way to maintain access to the latest features, performance improvements, and security updates. Customers running older PostgreSQL versions should review their upgrade plans and take advantage of available migration and upgrade resources to ensure a smooth transition to a supported version.
For customers who need additional time to complete their upgrades, Extended Support can help bridge the gap by providing continued support coverage and critical security updates beyond the end of standard support. We encourage customers to evaluate their PostgreSQL deployments, understand upcoming lifecycle milestones, and develop an upgrade strategy that aligns with their business needs.
Learn more: Azure Database for PostgreSQL flexible server extended support