Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id C804C9FA0EF for ; Sat, 9 Dec 2006 15:17:14 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 54086-04 for ; Sat, 9 Dec 2006 15:17:04 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by postgresql.org (Postfix) with ESMTP id A76809F9386 for ; Sat, 9 Dec 2006 15:17:06 -0400 (AST) Received: by py-out-1112.google.com with SMTP id a73so125749pye for ; Sat, 09 Dec 2006 11:17:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LkDnmecU+J0w4WW3wk+wsJQLv8LdkOXC4YNPnl29ZUA/IFYz1NIvhgwcxhsQ4UICZB7wbDysZWMSoi+DMJlwVmgBR4bJoI2DuUZjRDls3UJv9v7VnfcsfB+/bpkVHE8NbW4sjNp4efHtZLZLiexruLxBHCqLjz1Oev/JAFk1GEk= Received: by 10.35.99.17 with SMTP id b17mr8410127pym.1165691824988; Sat, 09 Dec 2006 11:17:04 -0800 (PST) Received: by 10.35.80.10 with HTTP; Sat, 9 Dec 2006 11:17:04 -0800 (PST) Message-ID: Date: Sun, 10 Dec 2006 00:47:04 +0530 From: "Rajesh Kumar Mallah" To: "Tom Lane" Subject: Re: Should duplicate indexes on same column and same table be allowed? Cc: "Lista Postgres" In-Reply-To: <18891.1165686391@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8397.1165647371@sss.pgh.pa.us> <18891.1165686391@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/101 X-Sequence-Number: 23893 On 12/9/06, Tom Lane wrote: > "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. Sorry , i guess i digressed . Lemme put the question once again. psql> CREATE INDEX x on test (col1); psql> CREATE INDEX y on test (col1); What is (are) the downsides of disallowing the second index. which is *exactly* same as previous? Regds mallah. > > regards, tom lane >