Re: Tricky bugs in concurrent index build - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Tricky bugs in concurrent index build
Date
Msg-id 87y7tcua5x.fsf@enterprisedb.com
Whole thread Raw
In response to Re: Tricky bugs in concurrent index build  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Tricky bugs in concurrent index build
Re: Tricky bugs in concurrent index build
List pgsql-hackers
Bruce Momjian <bruce@momjian.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.

That doesn't sound like English at all to me.

Fwiw, I think the best option was what Tom did. The gotcha I tripped on seems
pretty minor to me.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "Martin Atukunda"
Date:
Subject: Re: [PATCHES] psql 'none' as a HISTFILE special case
Next
From: Peter Eisentraut
Date:
Subject: Re: [GENERAL] invalid byte sequence ?