Re: Per-role disabling of LEAKPROOF requirements for row-level security?

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, Andreas Lind <andreaslindpetersen(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Per-role disabling of LEAKPROOF requirements for row-level security?
Date: 2025-06-16 17:21:32
Message-ID: aFBSnMJRugucQkja@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sorry for going on a bit of a tangent, but why is enum_eq not marked
leakproof when its code looks like this?

Datum
enum_eq(PG_FUNCTION_ARGS)
{
Oid a = PG_GETARG_OID(0);
Oid b = PG_GETARG_OID(1);

PG_RETURN_BOOL(a == b);
}

The only previous discussion I see [0] points to discussion about enum_cmp,
which seems to be more obviously non-leakproof due to its use of
enum_cmp_internal().

[0] https://postgr.es/m/14749.1550679857%40sss.pgh.pa.us

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-06-16 17:36:20 Re: Per-role disabling of LEAKPROOF requirements for row-level security?
Previous Message Andrey Borodin 2025-06-16 17:11:31 Re: amcheck support for BRIN indexes