Re:Postgres UUIDv7 and per-back end monotonicity
by reshlo on Thursday January 02, 2025 @05:26PM
(#42579633)
> Normally, time-based UUIDs from this document will be monotonic due to an embedded timestamp; however, implementations can guarantee additional monotonicity via the concepts covered in this section.
“Normally, I am at home because I do not have a reason to go out; however, sometimes I am at home because I am sleeping.”
Notice how this statement does not actually mean that I am always at home.
Re:Postgres UUIDv7 and per-back end monotonicity
by Dylan16807 on Thursday January 02, 2025 @05:32PM
(#42579694)
"this monotonicity" that OP suggests people not use is specifically the additional monotonicity.
Or to put it another way: OP is suggesting you don't depend on it being properly monotonic, because the default is that it is only partially monotonic.
The use of rand_a for extra monotonicity is optional. The monotonicity itself is not optional.
§5.7 states:
Guaranteeing additional monotonicity means that there is already a 'base' level of monotonicity, and there are provisions for even more ("additional") levels of it. This 'base level' is why §6.2 states: "Backbone of time-based sortable UUIDs"; "additional monotonicity". Additional: adding to what's already there.* https://datatracker.ietf.org/doc/html/rfc9562