What REPACK (CONCURRENTLY) costs while it runs

The blog post discusses the features and performance of the REPACK (CONCURRENTLY) command in PostgreSQL 19 compared to the older pg_repack and pg_squeeze tools. It provides an in-depth analysis of how REPACK operates online without locking the table, its efficiency in memory management, and its impact on write operations during execution. The author shares insights from practical tests and highlights potential issues when running long repacks on busy tables. Ultimately, the author recommends REPACK (CONCURRENTLY) as the optimal solution for managing bloated tables in PostgreSQL 19 and beyond.