Thursday, November 19, 2026

01Top stories

Primary intelligence

PostgreSQL 19 ships online repacking, plan advice and replica read-your-writes

Publisher-provided image for PostgreSQL 19 ships online repacking, plan advice and replica read-your-writes
Image: postgresql.org

The PostgreSQL Global Development Group released PostgreSQL 19 on November 19. The release adds `REPACK (CONCURRENTLY)` for reclaiming table bloat without blocking normal reads and writes, `pg_plan_advice` for influencing planner choices, and `WAIT FOR LSN` to support read-your-writes consistency on standbys. Developers also gain `INSERT ... ON CONFLICT DO SELECT` for get-or-create patterns and JSON output from `COPY`.

Other changes include parallel autovacuum index processing, improved replication behavior, more I/O observability and default JIT disabling. These are substantive operational improvements, but teams should benchmark workloads and validate extension compatibility before upgrading.

Why it matters

Core database maintenance and consistency improvements reduce downtime and application workarounds.

via PostgreSQL official release
Read full briefing Collapse briefing

Detailed briefing

Maintenance without long exclusive locks

The new REPACK operation reclaims space and can reorder table data, while its CONCURRENTLY mode is designed to keep normal reads and writes available. This addresses a familiar tradeoff with VACUUM FULL and CLUSTER, which remain for compatibility. Autovacuum gains parallel index processing and workload-priority scoring, while additional statistics views expose locks, recovery and vacuum priorities.

Planner control and replica consistency

The pg_plan_advice extension provides a way to influence query plan selection and store advice for repeat use, helping teams respond to regressions without rewriting application SQL. WAIT FOR LSN lets a standby wait until it has replayed a specified write-ahead log position before a dependent read, addressing the classic lag-induced read-your-writes problem. Logical replication also gains sequence-value support and simpler WAL-level setup.

Developer ergonomics and migration considerations

INSERT ON CONFLICT DO SELECT returns an existing conflicting row, simplifying get-or-create round trips. COPY gains JSON output, window functions gain IGNORE NULLS, and foreign-key checks and NOT IN planning receive optimizations. JIT is now disabled by default because its cost estimation proved unreliable. Operators should test extension compatibility, SQL semantics, query plans, replication behavior and rollback procedures before production upgrades.

Limitations & caveats

A major-version upgrade still requires extension, compatibility and workload testing; vendor benchmarks are not universal.