On Dec 23, 2009, at 1:15 PM, Tom Lane <[email protected]> wrote:
Robert Haas <[email protected]> writes:
On Dec 23, 2009, at 3:52 PM, Tom Lane <[email protected]> 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
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
