Postgres 19 adds built-in REPACK for concurrent table bloat cleanup
Original title: Postgres 19 Repack: Faster, Built-In Table Bloat Cleanup
REPACK CONCURRENTLY keeps the table readable and writable and takes only a brief lock at the end.
A Snowflake engineering post describes REPACK in Postgres 19 as a built-in way to reclaim space from bloated tables without an extension. REPACK CONCURRENTLY uses logical decoding, leaves the table readable and writable, and takes only a brief lock at the end. It is presented as a successor to VACUUM FULL downtime and to the pgrepack and pgsqueeze extensions.
Unconfirmed: The 50% bloat threshold is the author's rule of thumb, not a Postgres requirement.
- VACUUM FULL holds a read/write lock for the entire rebuild.
- pgrepack captured changes with triggers and an external client.
- pgsqueeze used WAL logical decoding inside a background worker.
- The author treats dead-tuple ratios above 50% as worth investigating.
From the original article
10 min read at snowflake.com[](https://www. snowflake. com/en/)[](https://www.
By craigkerstiens · snowflake.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.