Re: Update docs for UUID data type - Mailing list pgsql-hackers

From Andy Alsup
Subject Re: Update docs for UUID data type
Date
Msg-id CADOZ7s6XfnddptbssSx7vnOQRrOfCk+1yQzpfXkTd1Osc-wVfA@mail.gmail.com
Whole thread Raw
In response to Re: Update docs for UUID data type  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
Thank you for the clarification, and the well-worded paragraph. Please find the latest patch files attached.

Best regards,
Andy Alsup

On Tue, Feb 25, 2025 at 12:41 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Mon, 2025-02-24 at 21:04 -0500, Andy Alsup wrote:
> Please find the attached patch, which only addresses the UUID functions
> (in table format). I appreciate the comments related to the UUID datatype.
> If you feel like the additional content didn't add clarity, I certainly won't argue.

Your patch looks good to me.

I didn't mean that adding more information about the "uuid" data type is
a bad thing.  Perhaps that additional paragraph could be

    RFC 9562 defines 8 different UUID versions.  Each version has specific requirements
    for generating new UUID values, and each version provides distinct benefits and drawbacks.
    <productname>PostgreSQL</productname> provides native support for generating UUIDs
    using the UUIDv4 and UUIDv7 algorithms.  Alternatively, UUID values can be generated
    outside of the database using any algorithm.  The data type <type>uuid</type> can be used
    to store any UUID, regardless of the origin and the UUID version.

I would be happy if you added something like that again.

Yours,
Laurenz Albe
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [BUG]: the walsender does not update its IO statistics until it exits
Next
From: Michael Paquier
Date:
Subject: Re: Fix api misuse (src/bin/pg_amcheck/pg_amcheck.c)