Dearcolleagues, I wouldlike to present for discussion my attached new draft documentation on UUIDfunctions (Section 9.14. UUID Functions), which replaces the previouslyproposed draft at https://www.postgresql.org/docs/devel/functions-uuid.html.I have preserved and significantly supplemented the text that was there.
I have thefollowing goals: 1. Statethat from now on, the function uuidv7(), rather than autoincrement, is thedefault choice for generating primary keys 2. Describethe advantages of uuidv7() over autoincrement and uuidv4() 3. Refutethe often-cited imaginary disadvantages of UUIDv7 compared to autoincrement,such as: - Lower performance (see the refutation inthe article "UUID Benchmark War" https://ardentperf.com/2024/02/03/uuid-benchmark-war/) - Disclosure of date and time of recordcreation in the table (in reality, the timestamp offset parameter distorts thisinformation) 4. Confirm thefault tolerance of the uuidv7() function in all possible critical situations,namely: - System clock failure - Receiving an invalid value of the offsetargument, which would result in a timestamp overflow or a negative timestamp Regards, SergeyProkhorenko sergeyprokhore...@yahoo.com.au
UUID Functions.docx
Description: MS-Word 2007 document
UUID Functions.sgml
Description: Binary data
