Re: Unmark gen_random_uuid() function leakproof - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Unmark gen_random_uuid() function leakproof
Date
Msg-id CAD21AoCXboy7j0Yj53p8O=ou0+XjL_6gBq6bWYvStXbs1eB=UQ@mail.gmail.com
Whole thread Raw
In response to Re: Unmark gen_random_uuid() function leakproof  (Andres Freund <andres@anarazel.de>)
Responses Re: Unmark gen_random_uuid() function leakproof
List pgsql-hackers
On Mon, Dec 9, 2024 at 2:48 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Mon, Dec 9, 2024 at 2:23 PM Andres Freund <andres@anarazel.de> wrote:
> >
> > Hi,
> >
> > On 2024-12-09 14:10:30 -0800, Masahiko Sawada wrote:
> > > While reviewing UUIDv7 patch[1], I realized gen_random_uuid() is
> > > marked leakproof even though it doesn't take arguments. The functions
> > > without arguments don't need to be marked leakproof in principle. This
> > > is the sole function that has no arguments and is listed in the "List
> > > of built-in leakproof functions" in opr_sanity.sql. I've attached the
> > > patch for fixing it and for better consistency with new UUID
> > > generation functions discussed on that thread.
> >
> > Seems like it'd make sense to add a test to opr_sanity.sql so we don't
> > reintroduce such cases?
> >
>
> Thank you for the comment. It's a good idea. I've updated the patch.
>

I'm going to push the updated patch tomorrow, barring objections and
further comments.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: long-standing data loss bug in initial sync of logical replication
Next
From: Nathan Bossart
Date:
Subject: Re: Fix early elog(FATAL)