The PostgreSQL Global Development Group released PostgreSQL 19, introducing changes to database maintenance, query planning, replication, and application development. The release focuses on reducing administrative overhead and improving performance, with new tools for reorganizing tables without downtime and controlling query plans.
One of the main additions is REPACK, which reclaims unused table space and can reorder data to match an index. Its CONCURRENTLY option allows the operation to run without blocking reads or writes, making it a potential replacement for common uses of VACUUM FULL and CLUSTER. PostgreSQL 19 also introduces pg_plan_advice and pg_stash_advice, extensions that let administrators influence query plan selection and apply stored advice to queries by identifier, without changing application code.
Other maintenance improvements include parallel index vacuuming, changes to autovacuum prioritization, and additional monitoring views. EXPLAIN ANALYZE and related logging now report asynchronous I/O activity and WAL generated for full-page images. PostgreSQL also reports that changes to foreign key checks made bulk inserts nearly twice as fast in testing. Query planner improvements include more efficient anti-joins for eligible NOT IN clauses and eager aggregation before joins.
The release adds several features for replication and application development. Logical replication now supports sequence values, and PostgreSQL automatically raises the effective WAL level to logical when the first logical replication slot is created. The new WAIT FOR LSN command lets applications wait until a standby has replayed a specified WAL position before querying data, providing read-your-writes consistency. Developers also get INSERT ... ON CONFLICT DO SELECT for get-or-create operations, JSON output from COPY, additional SQL/JSON string methods, and IGNORE NULLS support for window functions.
Security and compatibility changes include server-side TLS Server Name Indication (SNI), which allows a server to present different certificates based on the hostname used by the client. PostgreSQL 19 also warns after successful MD5 password authentication. MD5 was deprecated in PostgreSQL 18 and is planned for removal in a future release, with SCRAM recommended instead. JIT compilation is now disabled by default because its cost estimates proved unreliable, while LZ4 becomes the default TOAST compression method when supported by the build.
The release has also prompted discussion on Hacker News about whether production users should wait for PostgreSQL 19.1.
Another user recommended waiting for the first minor release on critical production systems:
Personally, I would say, for critical production systems, it's still good to wait for the .1 release.
PostgreSQL 19 is available now. The complete list of changes is available in the official release notes.