Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>
>> I see we have:
>> CREATE index_opt_unique INDEX CONCURRENTLY index_name ...
>> which explains how this error occurs.
>>
>
> Maybe to you, but I'm still caffeine-deprived and don't exactly see what
> it was that Greg mistyped. AFAICS he'd have to type CONCURRENTLY twice
> to get into a scenario where the proposed warning would fire.
>
>
AAUI, he left off the index name so the first rule was matched rather
than the second, with "concurrently" being the index name.
cheers
andrew