Re: create index concurrently - duplicate index to reduce time without an index

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Gareth(dot)Williams(at)csiro(dot)au
Cc: mabewlun(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: create index concurrently - duplicate index to reduce time without an index
Date: 2010-06-02 12:49:19
Message-ID: AANLkTilzjIm92b8A8kAAw7SoKZgiFH8xr6i1eSIJIhoP@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jun 1, 2010 at 10:00 PM, <Gareth(dot)Williams(at)csiro(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Fetter 2010-06-02 13:28:14 Re: Is it possible to make the order of output the same as the order of input parameters?
Previous Message Craig Ringer 2010-06-02 12:36:00 Re: server-side extension in c++