Re: Row security violation error is misleading

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Row security violation error is misleading
Date: 2015-04-21 21:21:53
Message-ID: CAEZATCWJ5BmuojDhPSXMyB_6yUg28sp_2n1a6bYpTE1NLUhH-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21 April 2015 at 20:50, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Thanks a lot for this. Please take a look at the attached.

I've given this a quick read-through, and it looks good to me. The
interaction of permissive and restrictive policies from hooks matches
my expections, and it's a definite improvement having tests for RLS
hooks.

The only thing I spotted was that the file comment for
test_rls_hooks.c needs updating.

Is there any documentation for hooks? If not, perhaps that's something
we should be considering too.

Regards,
Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2015-04-21 21:30:39 Re: Reducing spinlock acquisition within clock sweep loop
Previous Message Robert Haas 2015-04-21 21:20:08 Re: Parallel Seq Scan