Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id CF0F49FA387 for ; Wed, 13 Dec 2006 19:56:00 -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 67875-03 for ; Wed, 13 Dec 2006 19:55:47 -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 39EA89FA248 for ; Wed, 13 Dec 2006 19:55:57 -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 kBDNtrZg013303; Wed, 13 Dec 2006 18:55:53 -0500 (EST) To: "Joshua D. Drake" cc: Bruce Momjian , Rajesh Kumar Mallah , Lista Postgres Subject: Re: Should duplicate indexes on same column and same In-reply-to: <1166054092.6494.4.camel@localhost.localdomain> References: <200612132349.kBDNn7S28850@momjian.us> <1166054092.6494.4.camel@localhost.localdomain> Comments: In-reply-to "Joshua D. Drake" message dated "Wed, 13 Dec 2006 15:54:52 -0800" Date: Wed, 13 Dec 2006 18:55:53 -0500 Message-ID: <13302.1166054153@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/192 X-Sequence-Number: 23984 "Joshua D. Drake" writes: >> The cost of preventing every stupid database use is too high. > Although a notice that says: > NOTICE: CREATE DUPLICATE INDEX y on test (col1); > Probably isn't out of order. You're omitting the (probably) several pages of C code that would be needed to detect whether the index is really a duplicate or not. regards, tom lane