Re: create index concurrently - duplicate index to reduce time without an index - Mailing list pgsql-general

From Scott Marlowe
Subject Re: create index concurrently - duplicate index to reduce time without an index
Date
Msg-id AANLkTilzjIm92b8A8kAAw7SoKZgiFH8xr6i1eSIJIhoP@mail.gmail.com
Whole thread Raw
In response to Re: create index concurrently - duplicate index to reduce time without an index  (<Gareth.Williams@csiro.au>)
List pgsql-general
On Tue, Jun 1, 2010 at 10:00 PM,  <Gareth.Williams@csiro.au> wrote:
> I'm concerned that just because I *can* create duplicate indexes, it doesn't mean I *should*.
> I'm worried it might actually break the service worse than the locking that I'm trying to avoid.
> Does anyone know which index will be used if there are duplicate ones and whether there is
> likely to be a problem?

I've done this dozens of times on a production server, midday, max
load, with no real problems.  create index concurrently is one of the
greatest things anyone's ever done for pgsql.

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: server-side extension in c++
Next
From: David Fetter
Date:
Subject: Re: Is it possible to make the order of output the same as the order of input parameters?