Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id D054C9FB434 for ; Fri, 2 Mar 2007 06:32:41 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 27281-02 for ; Fri, 2 Mar 2007 06:32:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id D8DFC9FA2FD for ; Fri, 2 Mar 2007 06:32:37 -0400 (AST) Received: from [10.1.44.241] (unknown [130.226.7.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by svr2.hagander.net (Postfix) with ESMTP id 12D4DDCC2D4; Fri, 2 Mar 2007 11:32:36 +0100 (CET) Message-ID: <45E7FD4E.6070101@hagander.net> Date: Fri, 02 Mar 2007 11:32:46 +0100 From: Magnus Hagander User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Tom Lane CC: Merlin Moncure , Benjamin Minshall , pgsql-performance@postgresql.org Subject: Re: stats collector process high CPU utilization References: <45CB5D06.7090004@intellicon.biz> <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> <17817.1172789069@sss.pgh.pa.us> <28377.1172799353@sss.pgh.pa.us> In-Reply-To: <28377.1172799353@sss.pgh.pa.us> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/51 X-Sequence-Number: 23456 Tom Lane wrote: > "Merlin Moncure" writes: >> On 3/2/07, Tom Lane wrote: >>> "Merlin Moncure" writes: >>>> 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? > >> I was referring to this: >> http://archives.postgresql.org/pgsql-hackers/2007-02/msg01418.php > > Oh, the kernel-panic thing. Hm, I wouldn't have thought that replacing > a file at a huge rate would induce a kernel panic ... but who knows? > Do you want to try installing the one-liner patch and see if the panic > goes away? > > Actually I was wondering a bit if that strange Windows error discussed > earlier today could be triggered by this behavior: > http://archives.postgresql.org/pgsql-general/2007-03/msg00000.php I think that's very likely. If we're updaitng the file *that* often, we're certainly doing something that's very unusual for the windows filesystem, and possibly for the hardware as well :-) //Magnus