Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D71272E004A for ; Wed, 27 Feb 2008 01:38:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 82224-04 for ; Wed, 27 Feb 2008 01:38:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2AEA32E0040 for ; Wed, 27 Feb 2008 01:38:53 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m1R5cngS014266; Wed, 27 Feb 2008 00:38:49 -0500 (EST) To: "Markus Bertheau" cc: "Scott Marlowe" , "Joshua D. Drake" , "Peter Koczan" , pgsql-performance Subject: Re: disabling an index without deleting it? In-reply-to: <684362e10802262129w4fe41264p1eb75cadd5f4d259@mail.gmail.com> References: <4544e0330802261246t574167fdpc47629d1bbe64fed@mail.gmail.com> <20080226130339.64bd4ec3@commandprompt.com> <9050.1204064560@sss.pgh.pa.us> <684362e10802261848j79686752k6dfbe032e985b131@mail.gmail.com> <13604.1204087729@sss.pgh.pa.us> <684362e10802262129w4fe41264p1eb75cadd5f4d259@mail.gmail.com> Comments: In-reply-to "Markus Bertheau" message dated "Wed, 27 Feb 2008 11:29:55 +0600" Date: Wed, 27 Feb 2008 00:38:49 -0500 Message-ID: <14265.1204090729@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/365 X-Sequence-Number: 28907 "Markus Bertheau" writes: > On the other hand, if the only reason to have that feature is to plan > and execute queries pretending that one index doesn't exist, then DROP > INDEX DEFERRED is not the most straightforward syntax. Yeah, I was just about to mention that 8.3 has a hook that allows a plug-in to manipulate the planner's notions of which indexes exist. Ignoring a specific index would be really trivial. regards, tom lane