Re: row_security GUC, BYPASSRLS - Mailing list pgsql-hackers

From Joe Conway
Subject Re: row_security GUC, BYPASSRLS
Date
Msg-id 55FC1A61.6070901@joeconway.com
Whole thread Raw
In response to Re: row_security GUC, BYPASSRLS  (Noah Misch <noah@leadboat.com>)
Responses Re: row_security GUC, BYPASSRLS  (Adam Brightwell <adam.brightwell@crunchydatasolutions.com>)
Re: row_security GUC, BYPASSRLS  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 09/18/2015 01:07 AM, Noah Misch wrote:
> Great.  Robert, does that work for you, too?  If so, this sub-thread is
> looking at three patches:
>
> 1. remove row_security=force
> 2. remove SECURITY_ROW_LEVEL_DISABLED; make ri_triggers.c subject to policies
> 3. add DDL-controlled, per-table policy forcing
>
> They ought to land in that order.  PostgreSQL 9.5 would need at least (1) and
> (2); would RLS experts find it beneficial for me to take care of those?

That would be awesome, but I would say that if we do #1 & 2 for 9.5, we
also need #3.

Joe


--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Use pg_rewind when target timeline was switched
Next
From: Teodor Sigaev
Date:
Subject: Re: [COMMITTERS] pgsql: Add pages deleted from pending list to FSM