From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Laszlo Nagy <gandalf@shopzeus.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: rebellious postgres process
Date: Tue, 04 Nov 2008 13:46:00 -0500
Message-ID: <25929.1225824360@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d10811041003u2100bb10v11e90763f12de58f@mail.gmail.com>
References: <490FFCF4.2050500@shopzeus.com>
<16117.1225804625@sss.pgh.pa.us>
<49106ED5.10805@shopzeus.com>
<dcc563d10811041003u2100bb10v11e90763f12de58f@mail.gmail.com>
"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
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: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, gandalf@shopzeus.com
Subject: Re: rebellious postgres process
In-Reply-To: <25929.1225824360@sss.pgh.pa.us>
* 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