Re: Tricky bugs in concurrent index build

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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.

i guess Greg is talking about something like(ie just forgetting to name
the index):

devel=# create index concurrently on foo ( a);
CREATE INDEX
devel=# \d foo
Table "public.foo"
Column | Type | Modifiers
--------+---------+-----------
a | integer |
b | text |
c | integer |
d | text |
Indexes:
"concurrently" btree (a)

Stefan