PostgreSQL 19 Beta has been announced, with general availability expected in September, following the project's yearly major-release cadence. This release introduces native SQL Property Graph Queries (SQL/PGQ), concurrent table repacking to reclaim storage without downtime, and a broad set of performance, observability, and administration improvements.
With SQL/PGQ support, the release enables graph queries over existing relational tables without requiring a separate graph database or data migration. PostgreSQL 19 also extends the asynchronous I/O framework introduced in v18 with automatic scaling of I/O workers, and adds the new pg_plan_advice and pg_stash_advice extensions for controlling and persisting query planner decisions. Maintenance operations see significant upgrades, including parallel autovacuum, smarter vacuum prioritization, reduced future vacuuming through automatic page visibility tracking, and a new REPACK command with a nonblocking CONCURRENTLY option for online table rebuilds.
According to the PostgreSQL Global Development Group's announcement, performance improvements are a major focus:
PostgreSQL 19 shows up to 2x better performance on inserts when foreign key checks are present. Additionally, this release improves several areas of the query planner and executor, including new anti-join optimizations, broader use of incremental sorts, eager aggregation that speeds up row processing, faster reads from storage during parallel sequential scans, and simplification of IS DISTINCT FROM and IS NOT DISTINCT FROM to plain <> and = operators when the inputs are not nullable. There are also improvements for LISTEN/NOTIFY scalability that impact multi-channel workloads.
Logical replication now automatically synchronizes sequence values, removing the need for manual reconciliation during major version upgrades, and can be enabled without a server restart, helping reduce planned downtime. René Cannaò, founder and CEO of ProxySQL, writes:
PostgreSQL 19 is introducing a feature that will eliminate a lot of messy backend workarounds: WAIT FOR LSN. (...) Historically, developers have thrown brittle hacks at this, like application sleep timers or forcing all post-write reads back to the primary database. With Postgres 19, read replicas can natively pause a session until they are perfectly caught up to a specific write.
Early community reaction suggests that while SQL/PGQ is the headline feature, PostgreSQL operators are more excited about the operational improvements. Christophe Pettus, CEO of PGX, comments:
The PG19 changes most likely to affect production behavior are not the headline features. The quiet flip of jit = off by default will change query plans and timings for analytics workloads that were silently benefiting (or suffering) from JIT compilation. The 64-bit MultiXactOffset finally retires the 4-billion-member wraparound risk that has bitten busy multi-row-locking workloads.
Cloud providers are already adopting PostgreSQL 19, with AWS making Beta 1 available in the RDS Database Preview Environment for evaluation in a fully managed setting. Ahead of the release, the community discussed the new pg_plan_advice and other expected features on Reddit. PGQViewer, an early sign of ecosystem adoption, is an open source graph explorer built for PostgreSQL 19. Mark Callaghan ran benchmarks on a small server, reporting that "Postgres continues to be boring in a good way. It is hard to find performance regressions."
Beta 1 builds, open items, and release notes are now available. Migrating data from previous releases requires a dump/restore using pg_dumpall, pg_upgrade, or logical replication.