From: Florian Weimer <fweimer@bfk.de>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Deadlock during CREATE INDEX CONCURRENTLY,
 but index still created
References: <82k4doujd2.fsf@mid.bfk.de>
	<BANLkTimKaXXjG6Ga5B+9=t5GtG5ofLUV2Q@mail.gmail.com>
Date: Wed, 18 May 2011 15:32:59 +0000
In-Reply-To: <BANLkTimKaXXjG6Ga5B+9=t5GtG5ofLUV2Q@mail.gmail.com> (Scott
	Marlowe's message of "Wed, 18 May 2011 09:33:17 -0600")
Message-ID: <828vu4uiqc.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

* Scott Marlowe:

> On Wed, May 18, 2011 at 9:19 AM, Florian Weimer <fweimer@bfk.de> wrote:
>> I've run two CREATE INDEX CONCURRENTLY on the same table in parallel,
>> and one of them errored out with:
>> The curious thing is that both indexes were created. =A0I would have
>> expected that the creation of idx1 would be rolled back.
>>
>> Are both of the usable, or should I re-create idx1 from scratch?
>
> They should be marked invalid.

Ah, thanks, I see it now.  I guess this answers my question. 8-)

--=20
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra=DFe 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99