Re: Row security violation error is misleading

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
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-25 00:47:54
Message-ID: 20150425004754.GX30322@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 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.

Fixed!

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

We don't generally document hooks beyond in the source code.. I'm happy
to expand on what's there, if anyone feels it'd be helpful to do so.
Having the test module is a form of documentation also, of course.

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-04-25 00:50:40 Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0
Previous Message Álvaro Hernández Tortosa 2015-04-25 00:11:43 Re: Fwd: [GENERAL] 4B row limit for CLOB tables