On Dec 22, 2009, at 7:31 PM, Tom Lane wrote:
> Wait a minute. I must have been looking at the wrong keyword list
> --- ON already is reserved. The problem is exactly that it can't
> tell whether CREATE INDEX CONCURRENTLY ON ... means to default the
> index name or to create an index named CONCURRENTLY. So really the
> *only* way to fix this is to make CONCURRENTLY be at least
> type_func_name_keyword.
+1 if it prevents indexes from being named "CONCURRENTLY".
Best,
David