Re: WIP patch (v2) for updatable security barrier views

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP patch (v2) for updatable security barrier views
Date: 2014-04-11 12:31:16
Message-ID: 20140411123116.GY2556@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Craig Ringer (craig(at)2ndquadrant(dot)com) wrote:
> > Hmm, the 'gotcha' I was referring to was the issue discussed upthread
> > around rows getting locked to be updated which didn't pass all the quals
> > (they passed the security_barrier view's, but not the user-supplied
> > ones), which could happen during a normal 'update' against a
> > security_barrier view, right?  I didn't think that would require the
> > view definition to be 'FOR UPDATE';
>
> It doesn't require the view to be defined FOR UPDATE.

Ok, great, glad I got that correct. :)

> I'll try to write an isolstiontester case to donstrate this on the weekend.

Great, thanks. I'll take a stab at writing up the 'gotcha' note tonight
or tomorrow.

Thanks again,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message lkcl . 2014-04-11 12:53:06 Re: [feature] cached index to speed up specific queries on extremely large data sets
Previous Message Bruce Momjian 2014-04-11 12:28:55 Re: [BUG FIX] Compare returned value by socket() against PGINVALID_SOCKET instead of < 0