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:54:52 -0500
Message-ID: <26115.1225824892@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d10811041048x4591f718pedb4f8da6084fc53@mail.gmail.com>
References: <490FFCF4.2050500@shopzeus.com>
<16117.1225804625@sss.pgh.pa.us>
<49106ED5.10805@shopzeus.com>
<dcc563d10811041003u2100bb10v11e90763f12de58f@mail.gmail.com>
<25929.1225824360@sss.pgh.pa.us>
<dcc563d10811041048x4591f718pedb4f8da6084fc53@mail.gmail.com>
"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
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: <26115.1225824892@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