Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)

From: "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Subject: Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)
Date: 2007-03-17 19:14:03
Message-ID: 45FC3DFB.8040303@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
>
> We need to be clear that we already have a solution to CREATE INDEX
> CONCURRENTLY. Do you agree that we do? Does anyone see a problem with
> the posted design for that?
>
> Hopefully it is only CREATE INDEX that we need to think about.
>

I agree. Lets first decide whether its only CREATE INDEX that
needs solution or its both.

Lets also decide whether we want to fix CREATE INDEX
[CONCURRENTLY] or we want to provide a seperate DLL to
CHILL the table and then build index normally. Tom
has already rejected the idea of holding exclusive lock
while chilling, but if we get around that, is rest of
the approach acceptable ?

If its going to be a seperate DLL, lets decide whether
its acceptable to run it as a seperate transaction.

Thanks,
Pavan

--

EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Saito 2007-03-17 19:23:58 Re: Bison 2.1 on win32
Previous Message Simon Riggs 2007-03-17 18:56:58 Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)