Re: RLS restrictive hook policies

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RLS restrictive hook policies
Date: 2015-08-03 19:36:29
Message-ID: 20150803193629.GX3587@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dean,

* Dean Rasheed (dean(dot)a(dot)rasheed(at)gmail(dot)com) wrote:
> On 3 August 2015 at 16:09, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > * Stephen Frost (sfrost(at)snowman(dot)net) wrote:
> >> Agreed. I'm happy to commit that change and back-patch it to 9.5,
> >> barring objections. Given that the only way to have restrictive
> >> policies currently is using hooks, I don't believe there's any
> >> documentation update required either; of course, I'll update the comment
> >> to reflect this discussion/decision and make any necessary changes to
> >> test_rls_hooks.
> >
> > Patch attached to make this change, with appropriate comment updates and
> > fixes to the test_rls_hooks modules.
> >
> > Comments?
> >
>
> Looks good to me.

Thanks! Pushed to master and 9.5.

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-08-03 20:08:14 Re: Re: Using quicksort and a merge step to significantly improve on tuplesort's single run "external sort"
Previous Message Peter Geoghegan 2015-08-03 19:33:15 Re: Using quicksort and a merge step to significantly improve on tuplesort's single run "external sort"