From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Problem with ALTER TABLE - occasional "tuple concurrently updated" |
Date: | 2010-11-18 02:57:09 |
Message-ID: | AANLkTim23nnhT7CKiLc5Z42N_KyucF9ENVM7bFi6Avaz@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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?
That does sound like a bug.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | amos | 2010-11-18 03:18:57 | BUG #5756: postgres eat up all memory(2GB memory) |
Previous Message | Bruce Momjian | 2010-11-18 02:54:33 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |