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

From Nathan Bossart
Subject Re: Per-role disabling of LEAKPROOF requirements for row-level security?
Date
Msg-id aFBSnMJRugucQkja@nathan
Whole thread Raw
In response to Per-role disabling of LEAKPROOF requirements for row-level security?  (Andreas Lind <andreaslindpetersen@gmail.com>)
Responses Re: Per-role disabling of LEAKPROOF requirements for row-level security?
List 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



pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: amcheck support for BRIN indexes
Next
From: Tom Lane
Date:
Subject: Re: Per-role disabling of LEAKPROOF requirements for row-level security?