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

From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Problem with ALTER TABLE - occasional "tuple concurrently updated"
Date: 2010-11-18 15:28:26
Message-ID: AANLkTikrmLMPjcZzMo2T-rknoQpt+e-hf=2uB44SNydd@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 17, 2010 at 8:57 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Nov 16, 2010 at 10:48 AM, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> wrote:
>> I have a process which runs in parallel creating tables which, as the
>> /final/ step in the import, gets SQL much like the following applied:
>>
>> ALTER TABLE foo INHERIT bar;
>>
>> Periodically, I get this error:  tuple concurrently updated
>>
>> Of course, I googled for the error message and see a bunch of issues
>> involving ANALYZE and even DROP function.
>> Is this the same root cause? Is there a fix? Is there a lock I could
>> take or some other approach that would prevent the error?
>> I thought all ALTER TABLE statements took a big fat lock to prevent
>> such an issue.
>
> The ALTER TABLE generates that error?  Is it running concurrently with
> any other DML?  What version of PostgreSQL is this?

Yes, sometimes yes, and 8.4.5.

> That does sound like a bug.

That's what I thought!

--
Jon

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Galkin 2010-11-18 16:49:09 BUG #5757: PL/PGSQL composite variable field error reporting
Previous Message Craig Ringer 2010-11-18 07:37:51 Re: BUG #5756: postgres eat up all memory(2GB memory)