On Tue, Jun 1, 2010 at 10:00 PM, <gareth.willi...@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. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
