Re: Update docs for UUID data type

Andy Alsup <bluesbreaker@gmail.com>

From: Andy Alsup <bluesbreaker@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Pgsql-Hackers Mailing List <pgsql-hackers@postgresql.org>
Date: 2025-02-27T03:11:25Z
Lists: pgsql-hackers

Attachments

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
>

Commits

  1. doc: Convert UUID functions list to table format.