On Sun, Feb 2, 2025 at 11:41 AM Sergey Prokhorenko
<sergeyprokhorenko@yahoo.com.au> wrote:
>
> Dear colleagues,
>
> I would like to present for discussion my attached new draft documentation on UUID functions (Section 9.14. UUID
Functions),which replaces the previously proposed draft at https://www.postgresql.org/docs/devel/functions-uuid.html. I
havepreserved and significantly supplemented the text that was there.
>
> I have the following goals:
>
> 1. State that from now on, the function uuidv7(), rather than autoincrement, is the default choice for generating
primarykeys
>
> 2. Describe the advantages of uuidv7() over autoincrement and uuidv4()
>
> 3. Refute the often-cited imaginary disadvantages of UUIDv7 compared to autoincrement, such as:
>
> - Lower performance (see the refutation in the article "UUID Benchmark War"
https://ardentperf.com/2024/02/03/uuid-benchmark-war/)
>
> - Disclosure of date and time of record creation in the table (in reality, the timestamp offset parameter distorts
thisinformation)
>
> 4. Confirm the fault tolerance of the uuidv7() function in all possible critical situations, namely:
>
> - System clock failure
>
> - Receiving an invalid value of the offset argument, which would result in a timestamp overflow or a negative
timestamp
>
Thank you for the proposal. Could you share the proposed document as a
.diff or .patch file? That would be easier to review the updates.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
