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.a...@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 >
v3-0001-docs-for-UUID-funcs-formatted-in-table.patch
Description: Binary data
v3-0002-docs-for-UUID-datatype-mention-UUID-versions.patch
Description: Binary data
