Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 0CBD99FB5C0 for ; Fri, 13 Apr 2007 00:49:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 83578-07 for ; Fri, 13 Apr 2007 00:49:55 -0300 (ADT) 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 559119FB5BC for ; Fri, 13 Apr 2007 00:49:55 -0300 (ADT) 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 l3D3nskm012361; Thu, 12 Apr 2007 23:49:54 -0400 (EDT) To: Steve cc: Scott Marlowe , PostgreSQL Performance Subject: Re: Strangely Variable Query Performance In-reply-to: References: <57271CC2-BCB1-4ACA-A177-4FF64F1BC33F@brandeis.edu> <16E9A17C-ADFA-43B2-B7EA-5C7A4D7E96D1@event-s.net> <0914C05F-BA1B-4A6C-A1B1-52256BC851A4@event-s.net> <1176396964.13754.16.camel@state.g2switchworks.com> <1176414724.13754.23.camel@state.g2switchworks.com> <1176416077.13754.26.camel@state.g2switchworks.com> <9833.1176418809@sss.pgh.pa.us> <10117.1176420763@sss.pgh.pa.us> <10355.1176422445@sss.pgh.pa.us> <10503.1176423606@sss.pgh.pa.us> Comments: In-reply-to Steve message dated "Thu, 12 Apr 2007 20:34:18 -0400" Date: Thu, 12 Apr 2007 23:49:54 -0400 Message-ID: <12360.1176436194@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/287 X-Sequence-Number: 24164 Steve writes: > Just dropping that index had no effect, but there's a LOT of indexes that > refer to receipt. So on a hunch I tried dropping all indexes that refer > to receipt date and that worked -- so it's the indexes that contain > receipt date that are teh problem. I'm still not having any luck reproducing the failure here. Grasping at straws again, I wonder if it's got something to do with the order in which the planner examines the indexes --- which is OID order. Could you send me the results of select indexrelid::regclass from pg_index where indrelid = 'detail_summary'::regclass order by indexrelid; regards, tom lane