| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RLS restrictive hook policies |
| Date: | 2015-08-03 15:26:40 |
| Message-ID: | CAEZATCVtjvRmxWCNCvkwzKPqLebnyGAw6A18Jdh26rwc-U9+5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3 August 2015 at 16:09, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Dean, all,
>
> * 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.
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-08-03 15:52:41 | Re: Minimum tuple threshold to decide last pass of VACUUM |
| Previous Message | Stephen Frost | 2015-08-03 15:09:34 | Re: RLS restrictive hook policies |