Postgres 19 Repack: Faster, Built-In Table Bloat Cleanup
craigkerstiens
45 points
5 comments
November 20, 2026
Related Discussions
Found 5 related stories in 147.0ms across 13,334 title embeddings via pgvector HNSW
- PostgreSQL 19 jascha_eng · 13 pts · November 19, 2026 · 60% similar
- PostgreSQL 19 linzhangrun · 56 pts · November 20, 2026 · 59% similar
- PostgreSQL 19 Released jkatz05 · 102 pts · November 19, 2026 · 57% similar
- Postgres isn't slow, your storage is saisrirampur · 172 pts · October 12, 2026 · 56% similar
- Postgres 19 is out, and it's available on Neon and Databricks Lakebase sp_from_db · 42 pts · November 20, 2026 · 55% similar
Discussion Highlights (2 comments)
jzelinskie
I haven't used these extensions, but I like the direction of being able to extend Postgres by tailing its own internals (pg_squeeze approach) than triggers (pg_repack). We (the SpiceDB developers) took a similar approach to solve a different problem a few years ago: implementing strict serializability in Postgres[0]. By hooking into the transactions layer themselves (pg_xact), we could layer on our own MVCC reusing the real Postgres transactions to compute visibility and total ordering. When you can just tail the Postgres internals, you don't even need to implement a Postgres extension, which can keep it portable across locked-down, managed Postgres offerings. Do folks know of other clever implementations of behavior by "spying" on the Postgres internals? [0]: https://m.youtube.com/watch?v=_f6fHy4DWWM
aurareturn
Trying to recoup space at a slow period, I remember using Repack on New Years Eve on my local computer for a multi TB production DB and waiting hours and hours hoping my connection doesn’t drop. When it dropped, I had to restart all over again. I thought it would be a simple process but it ended up taking many hours and a few retries. Holy hell it was a miserable experience and it ruined my New Years Eve. I’m so happy this is now built in.