Re: Tricky bugs in concurrent index build

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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:58:27
Message-ID: 24474.1156517907@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> The original thinking was to use CONCURRENT, and CREATE CONCURRENT INDEX
> sounded like a different type of index, not a different way to build the
> index. I don't think CONCURRENTLY has that problem, so CREATE
> CONCURRENTLY INDEX sounds good. To read in English, it would be read as
> CREATE CONCURRENTLY, INDEX ii.

OK, we've got two votes for that, so I'll make it so.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martin Atukunda 2006-08-25 15:03:55 Re: psql 'none' as a HISTFILE special case
Previous Message Bruce Momjian 2006-08-25 14:55:49 Re: Tricky bugs in concurrent index build