Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id CE0889F9C35 for ; Sat, 9 Dec 2006 15:45:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 16318-01 for ; Sat, 9 Dec 2006 15:45:22 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by postgresql.org (Postfix) with ESMTP id 9EE059F9386 for ; Sat, 9 Dec 2006 15:45:24 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id i28so1226074wxd for ; Sat, 09 Dec 2006 11:45:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=L/H0ViBIOXaIbX9bpUGRrKNa2DOVoFixy2kwLxbhCcZyiyxVyQjdJgYF11BpM9Q3PKxrWkbDv30XAhzhATeR3AG4WNac5VCrN7kOrRCyaqAEfpEgBepC5lvGF21Tf5tcd3melsWKFpSsyrN9O6Pe6uIIBBOQVecFcCfzs+VWVdc= Received: by 10.70.29.2 with SMTP id c2mr8647460wxc.1165693522941; Sat, 09 Dec 2006 11:45:22 -0800 (PST) Received: from 200-171-252-89.customer.telesp.net.br ( [200.171.252.89]) by mx.google.com with ESMTP id h37sm4897717wxd.2006.12.09.11.45.21; Sat, 09 Dec 2006 11:45:22 -0800 (PST) Subject: Re: Should duplicate indexes on same column and same table From: Daniel Cristian Cruz To: Lista Postgres In-Reply-To: References: <8397.1165647371@sss.pgh.pa.us> <18891.1165686391@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8 Date: Sat, 09 Dec 2006 17:45:25 -0200 Message-Id: <1165693525.5012.3.camel@debian> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/102 X-Sequence-Number: 23894 Em Dom, 2006-12-10 às 00:47 +0530, Rajesh Kumar Mallah escreveu: > 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? What if PostgreSQL make a NOTICE about this? The user could see it and take some action about it. Sincerely, -- Daniel Cristian Cruz クルズ クリスチアン ダニエル