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/

i feel you! dealing with scattered rows is such a pain, especially when performance takes a hit. pg_repack sounds like a game changer since it works online without locking the tables for long. has anyone tried it with large databases? curious how it holds up in real-world scenarios.