Snowflake ids fit this sort of thing better, and maintain temporal locality. I ran into this exact issue when building out a graph like database in Postgres ma

Snowflake ids fit this sort of thing better, and maintain temporal locality. I ran into this exact issue when building out a graph like database in Postgres many moons ago. It’s probably less of an issue with fast nvme sad drives now, but on mechanical drives ordering and locality are massive.