From: Scott Marlowe <scott.marlowe@gmail.com>
To: Laszlo Nagy <gandalf@shopzeus.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: rebellious postgres process
Date: Tue, 4 Nov 2008 11:03:30 -0700
Message-ID: <dcc563d10811041003u2100bb10v11e90763f12de58f@mail.gmail.com> (raw)
In-Reply-To: <49106ED5.10805@shopzeus.com>
References: <490FFCF4.2050500@shopzeus.com>
<16117.1225804625@sss.pgh.pa.us>
<49106ED5.10805@shopzeus.com>
On Tue, Nov 4, 2008 at 8:48 AM, Laszlo Nagy <gandalf@shopzeus.com> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, gandalf@shopzeus.com, tgl@sss.pgh.pa.us
Subject: Re: rebellious postgres process
In-Reply-To: <dcc563d10811041003u2100bb10v11e90763f12de58f@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox