• Sources: primary, discussion
  • Thread: PostgreSQL 19 release delay
  • Summary: REPACK replaces the VACUUM FULL and CLUSTER split and uses logical decoding like pg_squeeze. CONCURRENTLY needs twice the table and index space, a primary key, a non-partitioned logged table, and is not fully MVCC-safe for snapshots taken before it starts. Craig Kerstiens reports RC1 is out, RC2 is expected 2026-11-12, and GA later in November or December.
  • Why it matters: Teams that run pg_repack or pg_squeeze as extensions can plan to move bloat cleanup into core after upgrading to PostgreSQL 19.
  • Follow-up: PostgreSQL 19 RC2 expected 2026-11-12.