For all of its greatness and (mostly well deserved) praises, the lack of a reasonable cluster index capability (as in data order at storage layer) is Postgres' biggest limit IMHO.
Unfortunately, The CLUSTER command not only "blocks" the table for WRITE ops, but more importantly, it also blocks READ operations [0]. pg_repack helps, but is not always available when using a managed PG offering.
Not being able to control data ordering on disk is a potential deal breaker once the data reaches a certain size.
Unfortunately, The CLUSTER command not only "blocks" the table for WRITE ops, but more importantly, it also blocks READ operations [0]. pg_repack helps, but is not always available when using a managed PG offering.
Not being able to control data ordering on disk is a potential deal breaker once the data reaches a certain size.
[0]: https://www.postgresql.org/docs/current/sql-cluster.html