Received: from localhost (maia-5.hub.org [200.46.204.182])
	by postgresql.org (Postfix) with ESMTP id D36B89FB86A
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Thu,  1 Mar 2007 21:36:05 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024)
	with ESMTP id 63807-04 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Thu,  1 Mar 2007 21:35:51 -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 91CB89FB857
	for <pgsql-performance@postgresql.org>;
	Thu,  1 Mar 2007 21:35:56 -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 l221ZriA028378;
	Thu, 1 Mar 2007 20:35:53 -0500 (EST)
To: "Merlin Moncure" <mmoncure@gmail.com>
cc: "Benjamin Minshall" <minshall@intellicon.biz>,
	pgsql-performance@postgresql.org
Subject: Re: stats collector process high CPU utilization 
In-reply-to: <b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com> 
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>
	<b42b73150703011358p7dfe77dft85ba7f3cdd3ce160@mail.gmail.com>
	<17817.1172789069@sss.pgh.pa.us>
	<b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com>
Comments: In-reply-to "Merlin Moncure" <mmoncure@gmail.com>
	message dated "Fri, 02 Mar 2007 07:00:00 +0530"
Date: Thu, 01 Mar 2007 20:35:53 -0500
Message-ID: <28377.1172799353@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200703/35
X-Sequence-Number: 23440

"Merlin Moncure" <mmoncure@gmail.com> writes:
> On 3/2/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> "Merlin Moncure" <mmoncure@gmail.com> 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

			regards, tom lane