Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 77C4A1F02EF3 for ; Thu, 26 Apr 2012 15:23:57 -0300 (ADT) Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SNTMA-0004ru-6L for pgsql-performance@postgresql.org; Thu, 26 Apr 2012 18:23:56 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Thu, 26 Apr 2012 13:23:39 -0500 Message-Id: <4F994C5A02000025000473FD@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.2 Date: Thu, 26 Apr 2012 13:23:38 -0500 From: "Kevin Grittner" To: , "Richard Kojedzinszky" Subject: Re: query optimization References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201204/162 X-Sequence-Number: 46808 Richard Kojedzinszky wrote: > tuning our installation to not to use sequence scans in this case? Make sure effective_cache_size is set to the sum of shared_buffers and whatever your OS shows as usable for caching. Try adjusting cost factors: maybe random_page_cost between 1 and 2, and cpu_tuple_cost between 0.03 and 0.05. -Kevin