Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Saturday, 06-Jan-2024 01:54:53 JST feld

   in reply to

   • Michael
   @michael The indexes are not the primary bloat being solved with pg_repack, it's the tables. The indexes can always be rebuilt in place efficiently with
   
   REINDEX database_name CONCURRENTLY;
   
   pg_repack's main benefit is to rewrite the tables without the holes in them. Databases don't shrink the tablespace files as all those types of operations would be prohibitively expensive. Instead when you delete data it just leaves a hole in the file for it to maybe be reused later. The specifics here we not important, but this is the general idea.
   
   All RDBMS work this way, really.
   • Embed this notice
     Michael (michael@mstdn.thms.uk)'s status on Saturday, 06-Jan-2024 01:54:54 JST Michael

     Oopsie. Just back from a 1 hour downtime caused by my hard disk running out of space in the middle of the working day 🙈

     Back now thanks to pg_repack. Insane how much space the indexes waste on mastodon!

     #mastoadmin