PostgreSQL 19 introduces a built-in REPACK CONCURRENTLY feature that allows online table bloat cleanup without third-party extensions. Unlike VACUUM FULL which requires downtime, or tools like pg_repack that carry risk, this native feature reclaims bloated space while keeping tables fully readable and writable with only a brief lock at the end.
Background
PostgreSQL's MVCC design inherently causes table bloat as dead tuples accumulate from updates and deletes. Database administrators have historically relied on VACUUM FULL (downtime), pg_repack, or pg_squeeze to reclaim space.
- Source
- Lobsters
- Published
- Nov 4, 2026 at 06:44 AM
- Score
- 8.0 / 10