What Microsoft announced
Azure Database for PostgreSQL flexible server supports PostgreSQL 19 on the same day as the community release. Microsoft's PostgreSQL team blog says PostgreSQL 19 is available in East Asia during the preview. The same post says more regions are coming "soon" and gives no timetable. If your servers live anywhere else, nothing in the announcement says you can use PostgreSQL 19 yet.
The Azure Updates listing labels the offering "In preview." Azure's own legend defines that label as available to Azure customers for non-production use and testing. Microsoft's blog frames the preview the same way. It tells teams to use it to evaluate application compatibility, test the upgrade path and validate extension requirements ahead of broader availability. Treat this as a lab, not a production target.
Upgrading existing servers
New deployments can try PostgreSQL 19 right away. Microsoft says major version upgrade (MVU) lets you move eligible flexible server instances to PostgreSQL 19 in place. Microsoft doesn't define "eligible," so don't assume every server qualifies.
Pre-upgrade validation checks now accept PostgreSQL 19 as a target. Microsoft says to run them before upgrading to catch compatibility problems and blockers, and to fix those ahead of your maintenance window. It also states that major version upgrades require downtime. "In place" means less migration work, not zero downtime.
Microsoft's general major-version-upgrade documentation, last updated September 2026, adds practical detail. It isn't specific to PostgreSQL 19, and Microsoft says requirements vary by source and target version.
- Server name and connections: In-place upgrades keep the server name and settings. They don't require data migration or connection-string changes.
- Validation checks are safe to run: They don't change the server version, cause downtime or restart the server. Typical checks cover unsupported extensions, logical replication slots, prepared transactions, event triggers, unsupported object dependencies and pending restart-required configuration changes.
- Validation limits: The server must be in a Ready state. Checks aren't supported on read replicas. They can't run while another server operation is in progress.
- Free storage: Keep at least 10–20% free storage before upgrading.
- Backup and rollback: The service takes an implicit backup just before the upgrade. After a successful upgrade there is no automated way back. The documented fallback is a point-in-time restore to a time before the upgrade, onto a new server.
- HA servers: For servers with high availability, the service disables HA, upgrades the primary, then re-enables HA. Re-enabling needs enough capacity to provision a new standby.
- Geo-replication: It isn't supported during in-place upgrades. You must delete read replicas, including cascading ones, before upgrading the primary. You can re-create them afterward.
- After the upgrade: Run
ANALYZEin each database to refresh statistics. Stale statistics can cause poor query plans.
Extensions
Microsoft says key extensions are supported from day one. The announcement itself doesn't list them and points readers to the version-specific extension documentation. Microsoft's Ignite roundup does name some: pgvector, azure_ai, DiskANN, PostGIS and pg_duckdb are available alongside PostgreSQL 19. That isn't a complete list. Check the current documentation for names, versions and configuration requirements before you plan around any specific extension.
This matters because extensions are a common upgrade blocker. Microsoft's general documentation says some extensions must be dropped before an in-place upgrade and re-created afterward. The ones it names include pg_repack, hypopg and pg_partman. It also lists extensions blocked on particular version paths. Those lists were written before PostgreSQL 19 and may not cover this target, so run the validation checks against your own server.
What PostgreSQL 19 brings
Microsoft highlights three groups of upstream engine changes. These describe the engine, not Azure-specific benchmarks. The announcement gives no performance measurements.
- Maintenance: Parallel autovacuum can process a table's indexes with parallel workers. A new prioritization system steers maintenance toward tables that need it. A built-in
REPACKcommand reorganizes tables, and itsCONCURRENTLYoption lets reads and writes continue during the operation. - Query planning: The
pg_plan_adviceextension lets teams give guidance to the planner.pg_stash_advicecan apply stored advice based on query identifiers. Microsoft describes these as extra tools for investigating or managing plan behavior, not as a guarantee of better plans. - Data loading and integrity: Foreign-key checks are improved.
COPY FROMuses SIMD instructions to speed up delimiter scanning for text and CSV imports.
Microsoft also credits its upstream work for faster foreign-key checks, SIMD-accelerated COPY FROM parsing and reduced vacuum WAL generation. It says its contributors authored or co-authored 530 PostgreSQL 19 commits and reviewed 1,084. It cites a contribution snapshot shared at Ignite 2026. These are Microsoft's own figures.
Tooling and the supported-versions page
Azure's REST API release notes show a 2026-07-01-preview API version that adds PostgreSQL version 19 to the supported PostgresMajorVersion enumeration. Teams that manage servers through infrastructure-as-code should expect to need preview API versions to target it. Check your tooling before assuming it exposes the new version.
The supported-versions page, last updated in August 2026, still lists PostgreSQL 18 as the newest major version. It likely predates the preview, so don't read it as contradicting Microsoft's announcement. It does show where PostgreSQL 19 sits in the lineup. Version 18 has its own limitations on that page. Some extensions aren't supported on it, and the io_uring async I/O method can't be configured.
A suggested evaluation plan
- Stand up a PostgreSQL 19 test server in East Asia, or restore a copy of your data there to test the upgrade path.
- Run the pre-upgrade validation checks against a representative server, and note any blockers.
- Confirm every extension you rely on is supported on PostgreSQL 19 and meets its configuration requirements.
- Replay representative workloads and compare query plans. The new planner advice tools only matter if you have plan problems to solve.
- Time the upgrade on realistic data volumes. Microsoft says duration depends on database size and complexity, and long-running transactions can lengthen shutdown.
- Keep production on a generally available version until Microsoft announces broader availability.
Bottom line
This is a day-one preview, limited to one region and meant for non-production testing. The useful parts are the in-place upgrade path and validation-check support, which let teams rehearse a migration early. The engine features are interesting, but Microsoft hasn't published Azure benchmark data for them. I'd test the upgrade path now and wait to move production until Microsoft announces broader availability.
References
- (In preview) Public Preview: PostgreSQL 19 on Azure Database for PostgreSQL Azure Updates · 2026-11-19T23:25:49Z
- PostgreSQL 19 on Azure: Day-One Preview, MVU & Extensions techcommunity.microsoft.com
- Major Version Upgrades - Azure Database for PostgreSQL | Microsoft Learn learn.microsoft.com