On this page
The PostgreSQL Global Development Group released PostgreSQL 19 on 19 November 2026. The project's announcement leads with a new `REPACK (CONCURRENTLY)` command for rebuilding bloated tables without blocking reads and writes, and a new `pg_plan_advice` extension for steering the query planner. The release notes give the release date as 2026-11-19 and list several new system views. The full list of PostgreSQL 19 new features is long, and so is the list of changes that can affect an upgrade.
One point first: PostgreSQL 19 graph queries (SQL/PGQ) were a headline feature of the June beta, but they do not appear in the final announcement or in the release notes page we read. More on that below.
When was PostgreSQL 19 released?
PostgreSQL 19 was announced on 19 November 2026, according to the PostgreSQL front page and the release notes. The first beta had said the final release would come "around September/October 2026", so the final version arrived roughly a month later than that estimate.
The announcement points to the official downloads page, which lists installers and tools for Windows, Linux and macOS, and to the source code for version 19.0.
What are the headline PostgreSQL 19 new features?
The project groups its highlights into workload management, distributed data and developer experience.
- REPACK. The command reclaims unused space and can reorder a table to match an index. With `REPACK (CONCURRENTLY)` it does so without blocking reads or writes. It replaces `VACUUM FULL` and `CLUSTER`, which remain available for compatibility.
- Plan control. The `pg_plan_advice` extension lets users stabilise planner choices and experiment with alternatives using a "plan advice" mini-language. Its companion, `pg_stash_advice`, stores advice and applies it automatically by query identifier.
- Autovacuum. Autovacuum can vacuum indexes with parallel workers, set by the new `autovacuum_max_parallel_workers` setting, and uses a scoring system to choose which tables to process first.
- Replication. Logical replication can be enabled without a restart, sequence values can be replicated, and the new `WAIT FOR LSN` command gives "read-your-writes" consistency on standbys.
- SQL additions. `INSERT ... ON CONFLICT DO SELECT` supports the "get or create" pattern, `COPY` can output JSON, and window functions such as `lag()` and `lead()` can skip nulls with `IGNORE NULLS`.
- Speed. The project says improved foreign key checks made bulk inserts nearly twice as fast in its testing. That is the project's own figure and will vary by workload.
What are the new system views in PostgreSQL 19?
The release notes list these new views:
| View | What it reports |
|---|---|
| `pg_stat_lock` | Per-lock-type statistics |
| `pg_stat_recovery` | Recovery status |
| `pg_stat_progress_repack` | Progress of `REPACK`, `CLUSTER` and `VACUUM FULL` |
| `pg_stat_autovacuum_scores` | Per-table autovacuum details |
| `pg_dsm_registry_allocations` | Dynamic shared memory details |
The announcement also notes a new `IO` option for `EXPLAIN ANALYZE` that reports asynchronous I/O activity.
Does PostgreSQL 19 have graph queries?
The beta announcement said PostgreSQL 19 "introduces support for SQL/PGQ, letting users execute property graph queries using SQL standard syntax". InfoQ's June report described it as graph queries over existing relational tables without a separate graph database or data migration. A July article from Devart said the same, while warning that nothing was final until general availability.
However, the final announcement does not mention SQL/PGQ, and the release notes page we read contains no reference to property graphs. We could not confirm from official final-release pages that graph queries shipped in 19.0, so treat that as unverified until you check the release notes yourself.
What should you check before upgrading to PostgreSQL 19?
The release notes say migrating from any earlier release needs a dump and restore, `pg_upgrade` or logical replication. They also list compatibility changes that need action.
- JIT is off by default. The project says its cost estimates proved unreliable. Sites running many large analytical queries may want to turn it back on.
- Default TOAST compression is now `lz4`, when PostgreSQL is built with LZ4 support.
- `max_locks_per_transaction` default doubles from 64 to 128.
- `io_workers` is replaced by `io_min_workers` and `io_max_workers`, plus two further new I/O worker settings.
- RADIUS authentication is removed, and a successful `md5` login now produces a warning, which `md5_password_warnings` can switch off.
- `standard_conforming_strings` is forced on. Dumps made by older tools with it off will not load.
- Some clusters are refused by `pg_upgrade`, including those with `btree_gist` indexes on `inet` or `cidr`, or with CR or LF characters in database, role or tablespace names.
- Reindexing is recommended after `pg_upgrade` for full-text search and `pg_trgm` indexes, because character classification now follows the database locale provider.
- Monitoring changes. `pg_stat_subscription_stats.sync_error_count` is renamed, and some wait event names change.
What does it mean in practice? (Analysis)
This is our reading, not the project's. REPACK and `pg_plan_advice` both target problems that operators of busy databases have worked around with extensions or maintenance windows. Folding table rebuilding into core should simplify routine care, though the sensible approach is to test it on your own workloads first. The new views suggest a push towards observability of autovacuum and locking, which is where many production incidents begin.
The upgrade list is where teams should spend their time. Changes such as JIT, lock sizing and removed settings can alter behaviour without any application change, so a staging run against realistic data is a sensible first step. Anyone relying on RADIUS or MD5 needs a plan for authentication.
Sources
FAQ
Frequently asked questions
PostgreSQL 19 was released on 19 November 2026, according to the PostgreSQL project's announcement and the release notes, which list the release date as 2026-11-19.
The official PostgreSQL downloads page has installers and tools for Windows, Linux and macOS, and the source code for 19.0 is published on the project's site. Both are linked from the release announcement.
The release notes list pg_stat_lock, pg_stat_recovery, pg_stat_progress_repack, pg_stat_autovacuum_scores and pg_dsm_registry_allocations, among others.
SQL/PGQ property graph queries were announced as a feature in the June 2026 beta. The final announcement and the release notes page we read do not mention them, so we could not confirm them in 19.0.
The release notes say you can migrate from any earlier release using pg_dumpall, pg_upgrade or logical replication. Some clusters, such as those with certain btree_gist inet or cidr indexes, are refused by pg_upgrade until fixed.
Spotted an error? Tell us. Read how we report and correct stories in our editorial policy.
Written by
Mainstream Tech
Newsroom
News and analysis on technology, AI, business, politics and international affairs, from our newsroom in London.
More from Mainstream



