PostgreSQL 19 is out, and its headline feature attacks one of the oldest chores in running the open-source database: cleaning up bloated tables without locking everyone out. The PostgreSQL Global Development Group shipped the new major version on November 19, 2026, with a REPACK command that can rebuild a busy table while reads and writes carry on.
The database traces back to the POSTGRES project that Michael Stonebraker started at the University of California, Berkeley, in the mid-1980s, as Wikipedia’s history of PostgreSQL recounts, and the version numbers now arrive once a year. Until now, administrators reached for VACUUM FULL or CLUSTER to reclaim the dead space left behind by heavy updates and deletes. Both held the table hostage until they finished. According to the PostgreSQL 19 press release, REPACK takes over both jobs, and the REPACK (CONCURRENTLY) form does it without blocking traffic. The two old commands stay for compatibility.
“PostgreSQL 19 continues that commitment to reliability, giving users new ways to manage their workloads without disruption and to build applications that span multiple systems,” said Jonathan Katz, a member of the PostgreSQL core team, in the same announcement.
Five changes developers will notice
- Plan advice: a new pg_plan_advice extension lets teams pin or test query plans, and pg_stash_advice applies saved advice by query ID, so a slow plan can be fixed without touching application code.
- “Get or create” in one trip: INSERT … ON CONFLICT DO SELECT returns the row that already exists instead of failing quietly.
- Read-your-writes on replicas: a WAIT FOR LSN command lets a standby hold a query until it has caught up with a write made on the primary.
- JSON out of COPY: COPY TO can now emit JSON, including one single JSON array.
- Logical replication without a restart: creating the first logical replication slot raises the effective WAL level automatically, and sequence values can now be replicated too.
Faster without code changes
The project says reworked foreign key checks made bulk inserts nearly twice as fast in its testing. The planner can now turn NOT IN clauses into anti-joins when no NULLs are present and aggregate rows before a join. Autovacuum gains parallel index workers and a scoring system that decides which tables get attention first, and the asynchronous I/O system introduced in version 18 now scales its own worker count.
What could break an upgrade
The official PostgreSQL 19 release notes list several changes that deserve a read before anyone runs pg_upgrade. Just-in-time compilation is now off by default because its cost estimates proved unreliable; shops running large analytical queries may want to switch it back on. RADIUS authentication is gone, since the project only ever supported it over UDP. Successful md5 password logins now trigger a warning, the default for max_locks_per_transaction doubles from 64 to 128, and the rarely used MULE_INTERNAL encoding has been removed. Databases that use full text search or pg_trgm with ICU or builtin locales are advised to reindex after upgrading.
How long version 19 will be supported
Each major version gets five years of fixes. The project’s versioning policy lists November 19, 2031 as the final release date for version 19. That same table shows PostgreSQL 14 reached end of life on November 12, 2026, one week before the new release, so anyone still on 14 now has two reasons to plan a jump.
Recent security fixes in other server software have kept administrators busy, including the Java4Shell flaw in Java’s Base64 decoder. For another open-source project that lets teams host their own data, see how Protomaps packs a world map into a single file.
Minor releases for the 19 branch will follow the project’s usual schedule of at least one every three months.
Sources
- PostgreSQL 19 Press Kit, PostgreSQL Global Development Group, 2026
- Release Notes: PostgreSQL 19.0, PostgreSQL Global Development Group, 2026
- Versioning Policy, PostgreSQL Global Development Group, 2026
- PostgreSQL, Wikipedia, 2026
Image: Carl Lender, CC BY 2.0 via Wikimedia Commons
This article was produced with AI assistance and reviewed by our Editorial Desk. How we work.



