News for hackers. Stuff that matters.

A comment on The GitHub Availability Report. Parent comment

Re:The GitHub Availability Report by abhishekjha on Thursday July 16, 2020 @02:34AM (#23856418)
Isn't UUID discouraged for a PRIMARY KEY pertaining indexes?

What would the B+Tree look like for over 2 billions UUIDS where there is no order within? Also, the cache locality problem.

[ Parent | on HN ]
Re:The GitHub Availability Report by tasogare on Thursday July 16, 2020 @02:49AM (#23856484)
This is why GP wrote "It will give you UUIDs and the larger keyspace, without being excessively random (they're basically almost sequential)". The main point for not screwing up the clustered index is the "almost sequential" part.
[ Parent | on HN ]
Re:The GitHub Availability Report by dtech on Thursday July 16, 2020 @03:32AM (#23856702)
That is for random (v4) UUIDs. v1 UUIDs are mostly sequential in time on a single machine so don't have this problem, altough they do have problems that others indicated already.
[ Parent | on HN ]