Re: Postgres trigger side-effect is occurring out of order with row-level security select policy

2018-10-02 Thread Carl Sverre
the query. I have attached a psql session that demonstrates the exact performance issue I am referring to. Carl Sverre http://www.carlsverre.com On Tue, Oct 2, 2018 at 1:28 AM Dean Rasheed wrote: > On Mon, 1 Oct 2018 at 21:45, Carl Sverre wrote: > > Dean, > > Thank you

Re: Postgres trigger side-effect is occurring out of order with row-level security select policy

2018-10-02 Thread Carl Sverre
sible. Thank's to everyone for their contribution in figuring this out - much appreciated. Carl Sverre http://www.carlsverre.com On Mon, Oct 1, 2018 at 4:02 AM Dean Rasheed wrote: > The real issue here is to do with the visibility of the data inserted > by the trigger function from within

Re: Postgres trigger side-effect is occurring out of order with row-level security select policy

2018-10-01 Thread Carl Sverre
lo > > On 30.09.2018 23:31:32, Adrian Klaver wrote: > On 9/30/18 1:13 PM, Carl Sverre wrote: > > Thanks for the initial results. Can you check that you are not using > > super permissions and are enabling row security when running the test? > > Super ignores row security. > >

Re: Postgres trigger side-effect is occurring out of order with row-level security select policy

2018-10-01 Thread Carl Sverre
) < clavadetsc...@swisspug.org> wrote: > Hello > > > On 29.09.2018 20:24:45, Adrian Klaver wrote: > On 9/28/18 11:35 PM, Carl Sverre wrote: > > *Context* > > I am using row-level security along with triggers to implement a pure > > SQL RBAC implementation. While

Postgres trigger side-effect is occurring out of order with row-level security select policy

2018-09-29 Thread Carl Sverre
nserted in table 7. The id (fails) of the inserted row is returned If anyone can point me in the right direction I would be extremely thankful. Carl Sverre http://www.carlsverre.com