Re: Tricky bugs in concurrent index build

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Tricky bugs in concurrent index build
Date: 2006-08-25 15:21:27
Message-ID: 20060825152127.GF14622@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > What bothers me about what we have now is that we have optional keywords
> > before and after INDEX, rather than only between CREATE and INDEX.
>
> Yeah, putting them both into that space seems consistent to me, and
> it will fix the problem of making an omitted index name look like
> a valid command.
>
> I'm not sure I should be opening this can of worms, but do we want to
> use a different keyword than CONCURRENTLY to make it read better there?

The problem is that what the qualifier is doing is modifying the
operation itself, not the properties of the index to be created, like
UNIQUE, which modifies the index. So the qualifier should be something
that modifies the CREATE, that is, an adverb (AFAIK).

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-25 15:25:43 Re: Tricky bugs in concurrent index build
Previous Message Enver ALTIN 2006-08-25 15:17:45 Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM initscript