Re: tuple concurrently updated

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Kangmo, Kim" <ilvsusie(at)hanafos(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tuple concurrently updated
Date: 2002-07-28 09:02:44
Message-ID: Pine.NEB.4.44.0207281801330.527-100000@angelic.cynic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 25 Jul 2002, Tom Lane wrote:

> "Kangmo, Kim" <ilvsusie(at)hanafos(dot)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(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Curt Sampson 2002-07-28 09:06:12 Re: Virus Emails
Previous Message Robert E. Bruccoleri 2002-07-28 03:45:07 Re: Question about LWLockAcquire's use of semaphores instead of spinlocks