Re: Row Level Security − leakproof-ness and performance implications - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Row Level Security − leakproof-ness and performance implications
Date
Msg-id dd668f3d-eac8-6bfa-9174-661e63d1c837@2ndquadrant.com
Whole thread Raw
In response to Re: Row Level Security − leakproof-ness and performance implications  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2019-03-18 20:08, Peter Eisentraut wrote:
> I agree that it would be useful to document and discuss better which
> built-in operators are leak-proof and which are not.  But I don't think
> the CREATE POLICY reference page is the place to do it.  Note that the
> leak-proofness mechanism was originally introduced for security-barrier
> views (an early form of RLS if you will), so someone could also
> reasonably expect a discussion there.

It sounds like this will need significant additional work, so setting as
returned with feedback for now.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
Next
From: Andres Freund
Date:
Subject: Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits