Btree indices and UUIDv7

[hoerup]

I can see all of the postgresql indices/primary keys are created as btree AND I have also noted that a lot of the tables uses UUID as a primary key - but you are still using UUIDv4 values which due to their truly random nature are spread all over the range of valid values.

Which means that even values that are more or less timebased such as job_sessions, job_session_messages, job_session_objects are spread across the indices even though the newest entries should probably be grouped together

Please consider doing a research project on how a switch to UUIDv7 will impact performance especially on medium to large multi-tenant installations

[Polina]

Noted as well, as your previous feedback. I'm also passing this to our engineering team for review.
Thanks for sharing, and please keep it coming! )