Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D5F829FB39D for ; Thu, 1 Mar 2007 18:59:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 40173-05 for ; Thu, 1 Mar 2007 18:59:36 -0400 (AST) 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 54B0C9FA299 for ; Thu, 1 Mar 2007 18:59:40 -0400 (AST) 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 l21MiTcu017818; Thu, 1 Mar 2007 17:44:29 -0500 (EST) To: "Merlin Moncure" cc: "Benjamin Minshall" , pgsql-performance@postgresql.org Subject: Re: stats collector process high CPU utilization In-reply-to: References: <45CB5D06.7090004@intellicon.biz> <62089.75.14.32.120.1170994418.squirrel@intellicon.biz> <14668.1170995218@sss.pgh.pa.us> <20070209142459.GB4253@alvh.no-ip.org> <24717.1171033699@sss.pgh.pa.us> <29832.1171036557@sss.pgh.pa.us> <45CCA0DB.2010903@intellicon.biz> <1116.1171038786@sss.pgh.pa.us> <45CCBF13.2000707@intellicon.biz> <16282.1172779976@sss.pgh.pa.us> Comments: In-reply-to "Merlin Moncure" message dated "Thu, 01 Mar 2007 16:58:20 -0500" Date: Thu, 01 Mar 2007 17:44:29 -0500 Message-ID: <17817.1172789069@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/29 X-Sequence-Number: 23434 "Merlin Moncure" writes: > On 3/1/07, Tom Lane wrote: >> A further report led us to realize that 8.2.x in fact has a nasty bug >> here: the stats collector is supposed to dump its stats to a file at >> most every 500 milliseconds, but the code was actually waiting only >> 500 microseconds :-(. The larger the stats file, the more obvious >> this problem gets. > I think this explains the trigger that was blowing up my FC4 box. I dug in the archives a bit and couldn't find the report you're referring to? regards, tom lane