Gets better at every iteration...

Allow me a joke #DBAsRunCronjobs, and cronjobs run the World (and the mail-volume)

...up and running.
Thank You for maintaining those !

I have been guilty of experimenting with that, way back when global indexes on partitions were a Real Pain.

Things (global indxes in oracle) got a little better now.

hmmm that is not necessarily a Stamp of Quality...

You need to add #sarcasm to that ... Otherwise some innocent DBA will recommend it to his architect: UUIDV7 + Reverse index...

(I should have put bigger CAVEAT stmnts in the blog... )

This thing about "not spreading keys", hot-blocks, and index-contention, I think that is a double-edged sword.

It will depend on Your system, and Your typical load, whether you should pick V4 or V7. I suspect the actual differences will be marginal most cases.
Not many are That Extreme ? Are they?

Agree, That is the Whole Concept.
But both the neighbourpgs, and the python uuid pckge have functions to "extract" from a UUID: time, version, node...

And.. If there is "information" in there, some geek will want to peek into it...
(there is a ugly dutch word for someone who is bit-peek-happy)

Good to Hear. Thx for that.
I hadnt expected anything less.

Not often, but when I came across uuid-data (other database, and/or data-delivered to me) it was UUID-V4. The V7 is relatively Newly spec-ed.

Thx for that.

There is more XML out there than you think, notably in "back-ends".
Legacy from the 00s.

See it as a Tribute to the Longevity of some systems, datamodels, designs.

Data Lives Longer....

When using in python (set the module-property on a connection) it will take effect on the next call.

In oracle=pythondb, it piggybacks on actual calls, e.g. when Real work is done and does not cause an additional RT.

Kinda Curious for other drivers.

nb: Not Obsessed by RTs. Not Obsessed. Not.