PostgreSQL 19 Released with REPACK and New Replication Features

Original: PostgreSQL 19

Why This Matters

PostgreSQL 19 addresses long-standing pain points in live maintenance and HA replication setups.

PostgreSQL 19 launched November 19, 2026, adding a REPACK command for live table reorganization, logical replication of sequences, read-your-writes consistency on standbys, and parallel autovacuum of indexes.

PostgreSQL 19 ships with a range of performance and replication improvements. The new REPACK command reclaims disk space and reorganizes table data to improve query performance; REPACK CONCURRENTLY does the same without blocking reads or writes. Two new extensions accompany this release: pg_plan_advice for controlling query planner decisions, and pg_stash_advice for automatically applying plan advice based on query patterns.

On the replication front, logical replication can now be enabled without a server restart when wal_level is set to replica. Sequence values can also be logically replicated—a long-requested feature. Standbys gain read-your-writes consistency via a new WAIT command. Autovacuum gets parallel index processing and a scoring-based prioritization system. I/O worker processes now scale automatically, and foreign-key checks are faster.

Several breaking changes ship with v19: RADIUS authentication support is removed entirely (UDP-based RADIUS was deemed unfixably insecure), standard_conforming_strings is now permanently on server-side, and carriage returns or line feeds in database and role names are disallowed. The default index opclass for inet and cidr types switches from btree_gist to GiST due to correctness bugs in the former. Migration requires a dump/restore, pg_upgrade, or logical replication from any prior version.

Source

postgresql.org — Read original →