| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Tricky bugs in concurrent index build |
| Date: | 2006-08-25 14:06:23 |
| Message-ID: | 44EF03DF.8040905@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
>
>
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2006-08-25 14:08:18 | Re: Tricky bugs in concurrent index build |
| Previous Message | Tom Lane | 2006-08-25 14:01:00 | Re: Tricky bugs in concurrent index build |