PostgreSQL

UPDATE heavy workloads on PG are known to scatter rows around on pages which may increase IO when scanning many rows in a single query. Unless you are getting 100% HOT updates (most aren't).

To solve this in the past, I've used CLUSTER -- which isn't great because it requires a lock and takes a long time. It's almost unusable.

pg_repack solves this by doing online re-clustering and storage reclamation.

UPDATE heavy workloads on PG are known to scatter rows around on pages which may increase IO when scanning many rows in a single query. Unless you are getting 100% HOT updates (most aren't).

To solve this in the past, I've used CLUSTER -- which isn't great because it requires a lock and takes a long time. It's almost unusable.

pg_repack solves this by doing online re-clustering and storage reclamation.

https://reorg.github.io/pg_repack/

Wow, pg_repack sounds like a game changer for postgres! 🚀 gonna check it out, been struggling with those scattered pages too. thx for sharing! 🙌 