Re: Per-role disabling of LEAKPROOF requirements for row-level security? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Per-role disabling of LEAKPROOF requirements for row-level security?
Date
Msg-id 641899.1750095380@sss.pgh.pa.us
Whole thread Raw
In response to Re: Per-role disabling of LEAKPROOF requirements for row-level security?  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Per-role disabling of LEAKPROOF requirements for row-level security?
List pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes:
> Sorry for going on a bit of a tangent, but why is enum_eq not marked
> leakproof when its code looks like this?

Perhaps it could be, but I'm not sure how useful that is if we don't
mark the remaining enum comparison functions leakproof.

There might be a genuine hazard if something thinks it can substitute
use of enum_cmp for enum_eq, as indeed would happen in e.g. mergejoin.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Per-role disabling of LEAKPROOF requirements for row-level security?
Next
From: Tom Lane
Date:
Subject: Re: No error checking when reading from file using zstd in pg_dump