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

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(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 20:26:37
Message-ID: 20131105202637.GG14819@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-11-05 21:10:52 Add cassert-only checks against unlocked use of relations
Previous Message Kevin Grittner 2013-11-05 20:21:23 Re: missing locking in at least INSERT INTO view WITH CHECK