Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [GENERAL] Concurrency problem building indexes
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Wes <wespvp(at)syntegra(dot)com>, Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, "Jim C. Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [GENERAL] Concurrency problem building indexes
- Date: Tue, 25 Apr 2006 12:48:04 -0400
- Message-id: <20060425164804(dot)GA27351(at)surnet(dot)cl>
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.
- Follow-Ups:
- Catalog Access (was: [GENERAL] Concurrency problem building indexes)
- From: Jim C. Nasby
- Re: [GENERAL] Concurrency problem building indexes
- From: Tom Lane
- Catalog Access (was: [GENERAL] Concurrency problem building indexes)
- References:
- Re: [GENERAL] Concurrency problem building indexes
- From: Wes
- Re: [GENERAL] Concurrency problem building indexes
- From: Tom Lane
- Re: [GENERAL] Concurrency problem building indexes
- Prev by Date: Installation on Duel-Core Pentium XP
- Next by Date: Re: FOR UPDATE lock problem ?
- Previous by thread: Re: [GENERAL] Concurrency problem building indexes
- Next by thread: Re: [GENERAL] Concurrency problem building indexes
- Indexes: