Skip site navigation (1) Skip section navigation (2)

Re: Problem with ALTER TABLE - occasional "tuple concurrently updated"

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Problem with ALTER TABLE - occasional "tuple concurrently updated"
Date: 2011-03-19 02:12:58
Message-ID: AANLkTi=G=Q3kw0GQBaLKB1mOcEEdr37V_YhhQGdbik1y@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Mar 11, 2011 at 9:31 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Haas wrote:
>> On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> > Robert Haas wrote:
>> >> On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> >> > Was this fixed?
>> >>
>> >> Not yet. ?I can probably fix it, if nobody else wants to do it.
>> >
>> > Well, it has languished for five months, so the "nobody else wants" part
>> > is probably accurate. ?;-)
>>
>> OK.  Do we want to back-patch this, and if so how far?  On the one
>> hand, the symptom that OP is experiencing clearly sucks for him, but
>> on the other hand upgrading the strength of a lock in releases that
>> have been out in the field for a long time seems like an open
>> invitation to have the villagers show up with pitchforks.  Then again,
>> ShareUpdateExclusiveLock doesn't interfere with routine queries, so
>> maybe it's no big deal.  Given that we have only one report, I'm
>> inclined to just fix it in the master branch, but I could easily be
>> talked into the other approach if someone wants to make an argument
>> for it.
>
> Agree on master-only.

Done.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-bugs by date

Next:From: SrikanthDate: 2011-03-19 05:56:21
Subject: BUG #5936: Cannot connect to Server
Previous:From: Tom LaneDate: 2011-03-18 16:46:53
Subject: Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group