Re: "tuple concurrently updated" during index deletion

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Joe Conway" <mail(at)joeconway(dot)com>
Cc: "Hackers \(PostgreSQL\)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "tuple concurrently updated" during index deletion
Date: 2007-07-12 09:04:09
Message-ID: 1184231049.4263.3.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2007-07-11 at 16:49 -0700, Joe Conway wrote:
> On cvs head, I can get "tuple concurrently updated" if two separate
> transactions are both trying to drop the same index:

> ERROR: tuple concurrently updated

> The reason I ask is that someone contacted me who is seeing this on a
> production system, and the abort on session #2 is rolling back a large
> bulkload.

This situation will always cause an error on session #2, since if you
lock this more closely you'll get an ERROR because the object does not
exist.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2007-07-12 11:00:05 Re: doubt
Previous Message Gregory Stark 2007-07-12 08:57:40 Re: [GENERAL] Count(*) throws error