| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Row Level Security − leakproof-ness and performance implications |
| Date: | 2019-04-04 19:17:47 |
| Message-ID: | dd668f3d-eac8-6bfa-9174-661e63d1c837@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-04-04 19:23:08 | Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits |
| Previous Message | Alvaro Herrera | 2019-04-04 19:15:54 | Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits |