Re: Update docs for UUID data type

From: Andy Alsup <bluesbreaker(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Pgsql-Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Update docs for UUID data type
Date: 2025-02-28 01:50:16
Message-ID: CADOZ7s6+NEhGrBBxV36yOB27oxJKbgPRW=r+mbKe8Wbt7mb61Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Masahiko,

I have combined the gen_random_uuid() and uuidv4() into a single row, as
you suggested. Please find the v5 patch, which has been squashed into a
single commit.

Best regards,
Andy Alsup

On Thu, Feb 27, 2025 at 5:02 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
wrote:

> On Thu, Feb 27, 2025 at 1:26 PM Andy Alsup <bluesbreaker(at)gmail(dot)com> wrote:
> >
> > I've submitted it for the up-coming commitfest. The link is:
> https://commitfest.postgresql.org/patch/5604/
> > Thanks for all your help in reviewing these changes.
>
> Thank you for the patch!
>
> Regarding the 0001 patch, I think we can put uuidv4() and
> get_random_uuid() in the same row since they are effectively identical
> functions. For example, we have precedent such as char_length() and
> character_length().
>
> The 0002 patch looks good to me.
>
> Regards,
>
> --
> Masahiko Sawada
> Amazon Web Services: https://aws.amazon.com
>

Attachment Content-Type Size
v5-0001-Docs-for-UUID-funcs-formatted-in-table-and-UUID-d.patch application/octet-stream 8.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2025-02-28 01:53:19 Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?
Previous Message Zhang Mingli 2025-02-28 01:32:49 Re: Improve documentation regarding custom settings, placeholders, and the administrative functions