Re: [GENERAL] Concurrency problem building indexes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [GENERAL] Concurrency problem building indexes
Date
Msg-id 20060425164804.GA27351@surnet.cl
Whole thread Raw
In response to Re: [GENERAL] Concurrency problem building indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] Concurrency problem building indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Catalog Access (was: [GENERAL] Concurrency problem building indexes)  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
I'm late to this thread, but maybe we can make the process of storing
the new data in pg_class take a lock using LockObject() or something
like that to serialize the access to the pg_class row.  The idea would
be that this lock doesn't conflict with a LockRelation(), but it would
of course conflict with itself so no two CREATE INDEXES can enter that
code section concurrently.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Ben Clewett
Date:
Subject: Installation on Duel-Core Pentium XP
Next
From: Tom Lane
Date:
Subject: Re: FOR UPDATE lock problem ?