Re: tuple concurrently updated

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kangmo, Kim" <ilvsusie(at)hanafos(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: tuple concurrently updated
Date: 2002-07-25 20:25:48
Message-ID: 20755.1027628748@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"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 guess that is not a bug of pgsql, but a weak point of
> MVCC DBMS.

No, it's not a limitation of MVCC per se, it's only an implementation
shortcut for catalog updates. Fixing this across all system catalog
updates seems more trouble than it's worth. It'd be nice if the
concurrent-CREATE-INDEX case worked, though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kangmo, Kim 2002-07-25 20:34:25 Re: tuple concurrently updated
Previous Message Kangmo, Kim 2002-07-25 20:19:24 Re: tuple concurrently updated