Re: rebellious postgres process - Mailing list pgsql-admin

From Tom Lane
Subject Re: rebellious postgres process
Date
Msg-id 25929.1225824360@sss.pgh.pa.us
Whole thread Raw
In response to Re: rebellious postgres process  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Responses Re: rebellious postgres process  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-admin
"Scott Marlowe" <scott.marlowe@gmail.com> writes:
> On Tue, Nov 4, 2008 at 8:48 AM, Laszlo Nagy <gandalf@shopzeus.com> wrote:
>> 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.

Still, it's quite unclear how bad data read from the stats file could
have led to an infinite loop.  The stats file format is pretty "flat"
and AFAICS the worst effect of undetected corruption would be to have
wrong count values for some tables/databases.

            regards, tom lane

pgsql-admin by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: rebellious postgres process
Next
From: "Scott Marlowe"
Date:
Subject: Re: rebellious postgres process