Re: Review of Row Level Security - Mailing list pgsql-hackers

From Kohei KaiGai
Subject Re: Review of Row Level Security
Date
Msg-id CADyhKSV5yWwGvuOxMAUoeoH9q3E2ZjMT9ywSYiNYvx5+Z499Bw@mail.gmail.com
Whole thread Raw
In response to Re: Review of Row Level Security  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Review of Row Level Security
Re: Review of Row Level Security
List pgsql-hackers
2013/3/25 Simon Riggs <simon@2ndquadrant.com>:
> On 19 March 2013 15:08, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote:
>
>> It is much helpful if someone give me comments around these
>> arguable portions from the standpoint with fresh eyes.
>
> My feeling at this point is that I don't think I should commit this
> and related patches without more work.
>
> I certainly have time and willingness to do that in the next release
> cycle, but I feel like we need substantially longer to confirm that
> this is as rock solid as it needs to be.
>
> With everybody's permission, I'd like to move this to the next CF,
> with apologies to KaiGai.
>
I have to admit it will become time to move v9.4 development cycle
soon, and row-level security patch still needs some more works to
merge into the core.
At least, it does not stand on 40km point at marathon.

One thing we need to consider is, the current version of RLS patch
has cut-down functionality about writer side on INSERT / UPDATE
commands. So, we anyway needed to work on this feature on v9.4
development cycle.
So, I can agree to move this patch to the v9.4 development cycle.
Also, I'd like to have discussion for this feature in earlier half of
v9.4 to keep time for the remaining features, such as check on
writer-side, integration with selinux, and so on.

Thanks,
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>



pgsql-hackers by date:

Previous
From: Greg Jaskiewicz
Date:
Subject: Proof of concept: using genetic algorithm to come up with most optimal PostgreSQL.conf
Next
From: Kohei KaiGai
Date:
Subject: Re: Review of Row Level Security