Re: rebellious postgres process

"Scott Marlowe" <scott.marlowe@gmail.com> writes:
> On Tue, Nov 4, 2008 at 11:46 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> True.  Is it possible some other bit of the data in the system was
> corrupted and freaking out the stats collector?

The collector is pretty self-contained by design, so it's hard to see
what else would affect it.  I'm wondering a bit if the OP's hardware is
still flaky :-(.  In any case it would sure be interesting to see a few
stack traces from the process.

            regards, tom lane