Table repacking, done right
October 21–24
Level: Intermediate
There's always been a need for a mechanism to get rid of table bloat. VACUUM FULL does that already, but it comes with a potentially long period during which the table cannot be accessed or modified. Users discover to much frustration that Postgres does not offer any solutions to this problem, and they eventually turn to external tools.
Enter REPACK CONCURRENTLY. Intended to be integrated in Postgres 19, we hope it will offer peace of mind to thousands of DBAs around the world. But what is it? How does it work? We intend to explain all that every user will need to know about it, and then some.
