The PostgreSQL Global Development Group said on November 19, 2026 that it has released PostgreSQL 19. Tables with many updates and deletes build up unused space, called bloat, which can hurt query speed. The older fixes, VACUUM FULL and CLUSTER, blocked access to the table until they finished. The new REPACK (CONCURRENTLY) command reclaims that space without blocking reads or writes. The pg_stash_advice extension stores query-plan advice and applies it by query identifier, so users can fix a slow plan without changing the application.
A new WAIT FOR LSN command lets a session on a standby server wait until it has replayed the log up to a set point, so an app can read data it just wrote on the primary. The group said the foreign key check improvements made bulk inserts nearly 2x faster in its testing, and did not say what setup it tested on. Simon Willison said the release came two months after the usual September, mainly because of AI-reported security issues. The group's announcement gives no reason for the date.
The release targets workarounds teams built around bloat, stale replicas and plan changes. Leaders can ask which workloads would use REPACK (CONCURRENTLY), whether apps already work around replica lag, and who owns the JIT and md5 changes. JIT is now off by default because its cost estimates proved unreliable. md5 logins now trigger a warning.