Re: Should duplicate indexes on same column and same table be allowed? - Mailing list pgsql-admin

From Tom Lane
Subject Re: Should duplicate indexes on same column and same table be allowed?
Date
Msg-id 18891.1165686391@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should duplicate indexes on same column and same table be allowed?  ("Rajesh Kumar Mallah" <mallah.rajesh@gmail.com>)
Responses Re: Should duplicate indexes on same column and same table be allowed?  ("Rajesh Kumar Mallah" <mallah.rajesh@gmail.com>)
Re: Should duplicate indexes on same column and same tablebe allowed?  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-admin
"Rajesh Kumar Mallah" <mallah.rajesh@gmail.com> writes:
> Suppose an index get corrupted. And you need create a new index
> with exact specs and then drop the old index. Is it better to
> have a performing corrupted index or not have it at all and temporarily
> suffer some performance degradation ?

The case that was being discussed just a day or two ago was where you
wanted to do the equivalent of REINDEX because of index bloat, not any
functional "corruption".  In that case it's perfectly clear that
temporarily not having the index isn't acceptable ... especially if
it's enforcing a unique constraint.

            regards, tom lane

pgsql-admin by date:

Previous
From: "Rajesh Kumar Mallah"
Date:
Subject: reloading config files pg_ctl reload
Next
From: "Rajesh Kumar Mallah"
Date:
Subject: Re: Should duplicate indexes on same column and same table be allowed?