Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 33CAF650493 for ; Tue, 4 Nov 2008 14:19:30 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 81728-04 for ; Tue, 4 Nov 2008 14:19:29 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mail.postgresql.org (Postfix) with ESMTP id 8C339650511 for ; Tue, 4 Nov 2008 14:03:31 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id j4so1774121wah.19 for ; Tue, 04 Nov 2008 10:03:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=X29rRh+Njl8E/88rnluEKfzfNpff8MFwW9mM0qEgskg=; b=RJ8YFrxK8roo+WfMSNDa3+wCtoLZ97SnuiLhLXoov2ZMv0gusK17VWRJlkzW6NXFSO +7lvg8eMjr0a8lGA1pIneSGp3aaFBYfy7jAiW6ClEwtFpIGObDQmF2Ilzbn27CDQWICH RF7IV5eGjBCFnIIikSQXxrqfrBhB5oUgEgd+0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gguV5VedcMbNdGShPFpISrZ/xgU6nHQFhT5NKKiyQIZnEPhhk6odrF4bbC/xxzCX7y Qw4hpJfWk7Cc8VyfQ+tnsMiMVDcAGuQ1A4lD0VO6njctHA7gKMU9o4CasGdciaFOOSOP 3gvy2Rut0OLn4LkUZGpNuieNGNpfsRxJPEl0k= Received: by 10.114.157.3 with SMTP id f3mr1122036wae.40.1225821810453; Tue, 04 Nov 2008 10:03:30 -0800 (PST) Received: by 10.114.39.11 with HTTP; Tue, 4 Nov 2008 10:03:30 -0800 (PST) Message-ID: Date: Tue, 4 Nov 2008 11:03:30 -0700 From: "Scott Marlowe" To: "Laszlo Nagy" Subject: Re: rebellious postgres process Cc: "Tom Lane" , pgsql-admin@postgresql.org In-Reply-To: <49106ED5.10805@shopzeus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <490FFCF4.2050500@shopzeus.com> <16117.1225804625@sss.pgh.pa.us> <49106ED5.10805@shopzeus.com> X-Archive-Number: 200811/26 X-Sequence-Number: 30680 On Tue, Nov 4, 2008 at 8:48 AM, Laszlo Nagy wrote: > Tom Lane wrote: >> >> Huh, that's weird. We've fixed some bugs in the past that led the stats >> collector to consume excessive CPU --- but that was all pre-8.3. >> > > The server was rebooting intermittently, so we replaced the RAM (we got a > kernel page fault). But it was a week ago. The server is now stable. But is > it possible that somehow the file system became inconsistent, and that is > causing an infinite loop in the stats collector? Just guessing. Yes, you really can't trust any data that was written to the drives while the bad memory was in place.