Re: Tricky bugs in concurrent index build - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Tricky bugs in concurrent index build
Date
Msg-id 25326.1156519029@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tricky bugs in concurrent index build  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Tricky bugs in concurrent index build
Re: Tricky bugs in concurrent index build
List pgsql-hackers
Bruce Momjian <bruce@momjian.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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Safer auto-initdb for RPM init script
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCHES] psql 'none' as a HISTFILE special case