Re: tuple concurrently updated - Mailing list pgsql-hackers

From Curt Sampson
Subject Re: tuple concurrently updated
Date
Msg-id Pine.NEB.4.44.0207281801330.527-100000@angelic.cynic.net
Whole thread Raw
In response to Re: tuple concurrently updated  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tuple concurrently updated
List pgsql-hackers
On Thu, 25 Jul 2002, Tom Lane wrote:

> "Kangmo, Kim" <ilvsusie@hanafos.com> writes:
> > If the index on the same class,
> > two concurrent CREATE INDEX command can update pg_class.relpages
> > at the same time.
>
> Or try to, anyway.  The problem here is that the code that updates
> system catalogs is not prepared to cope with concurrent updates
> to the same tuple.

I see. So the error is basically harmless, and can be rectified anyway
with an ANALYZE, right?

cjs
-- 
Curt Sampson  <cjs@cynic.net>   +81 90 7737 2974   http://www.netbsd.org   Don't you know, in this new Dark Age, we're
alllight.  --XTC
 



pgsql-hackers by date:

Previous
From: "Robert E. Bruccoleri"
Date:
Subject: Re: Question about LWLockAcquire's use of semaphores instead of spinlocks
Next
From: Curt Sampson
Date:
Subject: Re: Virus Emails