Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 29F671FB5A4E for ; Sun, 15 Apr 2012 17:02:17 -0300 (ADT) Received: from sam.nabble.com ([216.139.236.26]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SJVeH-0006F5-NL for pgsql-performance@postgresql.org; Sun, 15 Apr 2012 20:02:15 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SJVe3-0006Ih-7r for pgsql-performance@postgresql.org; Sun, 15 Apr 2012 13:01:59 -0700 Date: Sun, 15 Apr 2012 13:01:59 -0700 (PDT) From: Filippos To: pgsql-performance@postgresql.org Message-ID: <1334520119128-5642356.post@n5.nabble.com> In-Reply-To: References: <4F7D76F50200002500046BFA@gw.wicourts.gov> Subject: Re: bad planning with 75% effective_cache_size MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.9 (/) X-Archive-Number: 201204/110 X-Sequence-Number: 46756 could you try to set the statistics parameter to 1000 (ALTER TABLE SET STATISTICS) for these tables, then run analyze and try again? -- View this message in context: http://postgresql.1045698.n5.nabble.com/bad-planning-with-75-effective-cache-size-tp5620363p5642356.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.