Horton
Menu

Re: creating index names automatically?

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <gsstark@mit.edu>, Alvaro Herrera <alvherre@commandprompt.com>, "David E. Wheeler" <david@kineticode.com>, Peter Eisentraut <peter_e@gmx.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2009-12-24T02:41:26Z
Lists: pgsql-hackers 
On Dec 23, 2009, at 1:15 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Robert Haas <robertmhaas@gmail.com> writes:
>> On Dec 23, 2009, at 3:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Uh ... I don't see what that fixes?  If CONCURRENTLY can be a column
>>> name this is still ambiguous.
>
>> How?
>
> Because CONCURRENTLY can still be reduced as tricky_index_name, so
> it still doesn't know how to parse CREATE INDEX CONCURRENTLY ON ...

It compiles without warnings for me. There's only one production that  
allows exactly one word between INDEX and ON.

...Robert