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

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: missing locking in at least INSERT INTO view WITH CHECK
Date: 2013-11-05 21:48:12
Message-ID: 1383688092.58848.YahooMailNeo@web162901.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2013-11-05 12:21:23 -0800, Kevin Grittner wrote:
>> Andres Freund <andres(at)2ndquadrant(dot)com>
>>
>>> Looks fine to me
>>
>> Any thoughts on whether this should be back-patched to 9.3?  I
>> can see arguments both ways, and don't have a particularly
>> strong feeling one way or the other.
>
> Hehe. I was wondering myself. I'd tentatively say no - unless we
> also backpatch the debugging patch there doesn't seem to be good
> reason to since the likelihood of conficts due to it doesn't seem
> very high.

Works for me.  Done.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-11-05 21:57:38 Re: Add cassert-only checks against unlocked use of relations
Previous Message Tom Lane 2013-11-05 21:45:49 Re: Add cassert-only checks against unlocked use of relations