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

From Robert Haas
Subject Re: row_security GUC, BYPASSRLS
Date
Msg-id CA+TgmoZ+giFihUaatPL9wjHy_XBhjc-_95GVkH2B5AstnnGRVA@mail.gmail.com
Whole thread Raw
In response to Re: row_security GUC, BYPASSRLS  (Stephen Frost <sfrost@snowman.net>)
Responses Re: row_security GUC, BYPASSRLS  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Sep 20, 2015 at 5:35 PM, Stephen Frost <sfrost@snowman.net> wrote:
> * Joe Conway (mail@joeconway.com) wrote:
>> 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.
>
> Agreed on all of the above.

Well, then, we should get cracking.  beta1 is coming soon, and it
would be best if this were done before then.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Limit GIST_MAX_SPLIT_PAGES to XLR_MAX_BLOCK_ID
Next
From: Tom Lane
Date:
Subject: Re: row_security GUC, BYPASSRLS