peter plachta <pplachta@gmail.com> writes: > The company I work for has a large (50+ instances, 2-4 TB each) Postgres > install. One of the key problems we are facing in vanilla Postgres is > vacuum behavior on high QPS (20K writes/s), random index access on UUIDs.
Indexing on a UUID column is an antipattern, because you're pretty much guaranteed the worst-case random access patterns for both lookups and insert/delete/maintenance cases. Can you switch to timestamps or the like?
There are proposals out there for more database-friendly ways of generating UUIDs than the traditional ones, but nobody's gotten around to implementing that in Postgres AFAIK.