Pull to refresh
Logo
PostgreSQL 19 comes to Azure on release day

PostgreSQL 19 comes to Azure on release day

New Capabilities

A preview in East Asia includes in-place major version upgrades and key extensions from day one

Overview

Updated 15 hours ago

PostgreSQL 19 came out on November 19, 2026. Microsoft opened a preview of the same version on Azure Database for PostgreSQL flexible server that day, in East Asia only, with in-place upgrades and key extensions available immediately.

The version number is the small part. Azure's claim is that the engine, the upgrade path for existing servers, and the extensions applications depend on all arrive together, instead of one at a time.

Why it matters

Teams on Azure can test PostgreSQL 19, the upgrade to it, and their extensions in one place, without a separate migration project.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

What’s new in this version?

PostgreSQL 19 adds a built-in REPACK command for online table reorganization, two planner-advice extensions (pg_plan_advice and pg_stash_advice) to stabilize query plans, parallel index vacuuming, and read-your-writes consistency on replicas via a new WAIT FOR LSN command.

The REPACK command replaces VACUUM FULL and CLUSTER without the downtime those tools required, and the planner-advice extensions let teams fix slow queries without changing application code.

4 details4 sources1 disagreement
  • REPACK (CONCURRENTLY) reclaims bloat and reorders table data to match an index while reads and writes continue; it replaces VACUUM FULL and CLUSTER, which remain for compatibility. It has limits: it needs a non-deferrable primary key or index-based replica identity, temporary disk space for a table copy, and fails if more than ~104 million tuples change during the operation [databricks.com](https://www.databricks.com/blog/postgresql-19-available-lakebase).
  • pg_plan_advice lets you experiment with planner choices using a mini-language; pg_stash_advice stores advice and auto-applies it by query identifier, so you can fix a slow plan without touching the application [postgresql.org](https://www.postgresql.org/about/news/postgresql-19-released-3449/).
  • Autovacuum can now vacuum indexes with parallel workers (autovacuum_max_parallel_workers) and uses a scoring system to prioritize tables; queries that read a table can mark pages all-visible during execution, cutting future vacuum work [postgresql.org](https://www.postgresql.org/about/news/postgresql-19-released-3449/).
  • Logical replication no longer requires a restart — the effective WAL level rises to logical automatically — and adds sequence-value replication, an EXCEPT clause in CREATE PUBLICATION, and WAIT FOR LSN so standby sessions can wait for replay before reading [postgresql.org](https://www.postgresql.org/about/news/postgresql-19-released-3449/).
Room for disagreement
  • Concurrent REPACK has real operational constraints — Databricks notes the ~104 million tuple change limit during the operation and the need for free replication-slot capacity, so the headline "no downtime" claim is narrower than it sounds for busy tables.
0 AI answers with web search. May be wrong.

Key Indicators

19
PostgreSQL major version released
The upstream release and the Azure preview landed on the same calendar day.
5
Extensions named for day-one availability
pgvector, azure_ai, DiskANN, PostGIS and pg_duckdb; Azure says the list is not exhaustive.
1
Azure regions with the preview at launch
East Asia only, with other regions to follow.

Voices

Curated perspectives — historical figures and your fellow readers.

Sign up to generate historical perspectives on this story.

Organizations Involved

Timeline

July 2026 November 2026

4 events Latest: Yesterday
Tap a bar to jump to that date
  1. PostgreSQL 19 released upstream

    Latest Release

    The PostgreSQL Global Development Group ships version 19 with a built-in REPACK command and two planner-advice extensions.

  2. Azure opens PostgreSQL 19 Preview in East Asia

    Release

    New servers can run version 19, and eligible existing servers can start an in-place major version upgrade.

  3. Pre-upgrade validation checks accept version 19

    Tooling

    The checks scan for unsupported extensions, replication slots, prepared transactions and pending restart-required settings before an upgrade runs.

  4. Azure API adds PostgreSQL 19 to its version list

    Product

    API version 2026-07-01-preview adds 19 to the supported major-version enumeration, four months before the engine shipped.

Scenarios

1

PostgreSQL 19 goes generally available on Azure

Likely Resolves by End of 2027

Discussed by: Azure's supported-versions documentation, which currently carries the Preview label

Azure keeps a separate page listing which versions are supported and how. General availability means the Preview label comes off that page and the version carries the service's standard backing. Microsoft has published no date for that step.

2

Preview spreads beyond East Asia

Likely Resolves by Q2 2027

Discussed by: Microsoft's launch post, which says more regions are coming without giving a schedule

The November 19 preview covers one region. Microsoft says additional regions will follow. A second region would show the preview is scaling rather than parked, and would let customers outside Asia test latency-sensitive workloads.

3

PostgreSQL 20 repeats the day-one pattern

Possible Resolves by Q1 2028

Discussed by: The PostgreSQL project's yearly release cadence, as described in Azure's upgrade documentation

PostgreSQL ships a major version about once a year, which points to version 20 in late 2027. A same-day Azure preview would show the release-day process has become routine. A gap would show November 19 was a one-time push rather than a new baseline.

Historical Context

2 moments from history that rhyme with this story — and how they unfolded.

Through November 2026

PostgreSQL's yearly major release cycle (through 2026)

The PostgreSQL Global Development Group ships a new major version roughly once a year, then follows it with minor releases that stay backward compatible. Major versions can include internal changes that break applications, so an upgrade is a testing job rather than a routine patch.

Then

An engine release is only usable once the extensions an application depends on also support it.

Now

Teams on managed PostgreSQL plan around a recurring yearly decision instead of a one-time migration.

Why this matters now

Version 19 is the 2026 edition. Azure's claim is that the extension and upgrade work no longer adds a separate wait on top of it.

Through November 2026

Azure's in-place major version upgrade (documented through 2026)

Azure flexible server upgrades major versions in place: the server keeps its name and settings, connection strings do not change, and no data migration is required. Azure says this is faster and involves shorter downtime than migrating data.

Then

The upgrade becomes an operation on the existing server rather than a parallel build.

Now

The remaining gate is compatibility: unsupported extensions, replication slots, prepared transactions and pending restart-required settings.

Why this matters now

Those are the items Azure's validation checks now scan for with version 19 as the target, which is what makes a same-day upgrade offer practical.

Sources

(4)