X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 1A1C3474E4F for ; Fri, 14 Feb 2003 12:00:17 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 5277A474E42 for ; Fri, 14 Feb 2003 12:00:16 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1EH0I5u008001; Fri, 14 Feb 2003 12:00:18 -0500 (EST) To: Scott Cain Cc: pgsql-performance@postgresql.org, gmod schema Subject: Re: performace problem after VACUUM ANALYZE In-reply-to: <1045241040.1486.600.camel@localhost.localdomain> References: <1045241040.1486.600.camel@localhost.localdomain> Comments: In-reply-to Scott Cain message dated "14 Feb 2003 11:44:00 -0500" Date: Fri, 14 Feb 2003 12:00:18 -0500 Message-ID: <8000.1045242018@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/83 X-Sequence-Number: 1139 Scott Cain writes: > [ much stuff ] Could we see EXPLAIN ANALYZE, not just EXPLAIN, output for all these alternatives? Your question boils down to "why is the planner misestimating these queries" ... which is a difficult question to answer when given only the estimates and not the reality. A suggestion though is that you might need to raise the statistics target on the indexed columns, so that ANALYZE will collect finer-grained statistics. (See ALTER TABLE ... SET STATISTICS.) Try booting it up to 100 (from the default 10), re-analyze, and then see if/how the plans change. regards, tom lane