Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id AF4602E0072 for ; Mon, 25 Feb 2008 19:32:18 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 23154-06 for ; Mon, 25 Feb 2008 19:32:15 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mx.mahope.net (u1da.mahope.net [74.53.48.71]) by postgresql.org (Postfix) with ESMTP id A34502E006C for ; Mon, 25 Feb 2008 19:32:15 -0400 (AST) Received: from mx.mahope.net (u1da.mahope.net [127.0.0.1]) by mx.mahope.net (Postfix) with ESMTP id 68CA734C278; Mon, 25 Feb 2008 23:32:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=wiggum.com; h=cc: message-id:from:to:in-reply-to:content-type: content-transfer-encoding:mime-version:subject:date:references; q= dns/txt; s=mail; bh=XAHj85nn4+19XbowXi74DXURZb0=; b=J7MiyCLVZUAy tWqCBTkufuNxJNfImjeuV9kTSzU6jFdGQCeArRho6tI0/JzlJP+XpThEw/DeQLXR UdmIbSg0RZjPcf/9ZMoDNWAVbchPNIgR+dxxHZESrwmi5EnFXarRllarW9eRaWur zwF6QgfVZ2r+XakZpfOdEcq2t7ncgNY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=wiggum.com; h=cc:message-id:from: to:in-reply-to:content-type:content-transfer-encoding: mime-version:subject:date:references; q=dns; s=mail; b=R8nWwDHvV m6Ssqiq5OQtwkERrhwmCuptBFrZwGrj8OvLOjd40XcLw4V5MU53iN7YbSKXmMyug HOfiLHiQSeOSv6wuQFsaZ7zvL8FO7UcErebLIFEhKdDfV0p9oUTqJycBLb4Kh4Ui xiiaY+I1Yz1YMBGypiWJcy4ZmiYkE2t07U= Received: from jomama.pvt.wiggum.com (jomama.wiggum.com [66.134.111.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.mahope.net (Postfix) with ESMTP id AB8B134C276; Mon, 25 Feb 2008 23:32:13 +0000 (UTC) Cc: "pgsql-performance" Message-Id: From: Sean Leach To: Stephen Denne In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Re: Weird issue with planner choosing seq scan Date: Mon, 25 Feb 2008 15:32:10 -0800 References: X-Mailer: Apple Mail (2.919.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.691 tagged_above=0 required=5 tests=DNS_FROM_OPENWHOIS=2.431, WHOIS_DMNBYPROXY=0.26 X-Spam-Level: ** X-Archive-Number: 200802/336 X-Sequence-Number: 28878 On Feb 25, 2008, at 2:59 PM, Stephen Denne wrote: >> > > Please know that I'm very new at advising PostgreSQL users how they > should tune their system... I'd never have known it if you hadn't said anything > > > My understanding of your vacuum verbose output was that it was > pointing out that max_fsm_pages was currently smaller than 281727, > so therefore there was no way it could contain mappings to all the > reusable space. However I don't think it is hinting at, nor > recommending a value that you should be using. > > If you do nothing, then this number of pages with reusable space > will probably continue to grow, therefore, it probably has been > growing. > > So, for example, if your max_fsm_pages is currently only 20000, then > perhaps 20000 of the 281727 pages with reusable space are in the > free space map. The remaining 260000 pages _may_ have been generated > through 20 different processes each of which created 13000 more > pages with reusable space than the map could reference. If that was > the case, then a max_fsm_pages of 33000 might be large enough. > > Do you see what I'm getting at? > I think that you should do a vacuum full of that table once, then > monitor the number of pages in it with reusable space for a while > (over a few iterations of your regular processes). That should give > you information about how much larger your max_fsm_pages should be > than it currently is. This sounds sane to me, will do. Thanks again!