Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 146B29F9392 for ; Sat, 9 Dec 2006 13:46:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 01120-08 for ; Sat, 9 Dec 2006 13:46:33 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2155A9FA0FB for ; Sat, 9 Dec 2006 13:46:34 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kB9HkVi6018892; Sat, 9 Dec 2006 12:46:31 -0500 (EST) To: "Rajesh Kumar Mallah" cc: "Lista Postgres" Subject: Re: Should duplicate indexes on same column and same table be allowed? In-reply-to: References: <8397.1165647371@sss.pgh.pa.us> Comments: In-reply-to "Rajesh Kumar Mallah" message dated "Sat, 09 Dec 2006 12:50:37 +0530" Date: Sat, 09 Dec 2006 12:46:31 -0500 Message-ID: <18891.1165686391@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/100 X-Sequence-Number: 23892 "Rajesh Kumar Mallah" 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