Re: missing locking in at least INSERT INTO view WITH CHECK

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: missing locking in at least INSERT INTO view WITH CHECK
Date: 2015-09-08 21:05:04
Message-ID: 20150908210504.GT3685@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Andres Freund (andres(at)anarazel(dot)de) wrote:
> On 2015-08-27 18:37:10 +0100, Dean Rasheed wrote:
> > Yes, I concur. It now needs an acquireLocksOnSubLinks_context with
> > for_execute = true, but otherwise it should work.
>
> Ok, I'll push that then, unless somebody else wants to do the honors.

Done. Apologies about it taking so long, the TAP test failure issue
with 'make check' had me tied up for a bit.

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-09-08 21:11:36 Re: why can the isolation tester handle only one waiting process?
Previous Message Tomas Vondra 2015-09-08 21:02:27 Re: DBT-3 with SF=20 got failed