From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Laszlo Nagy" <gandalf(at)shopzeus(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: rebellious postgres process |
Date: | 2008-11-04 18:54:52 |
Message-ID: | 26115.1225824892@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Tue, Nov 4, 2008 at 11:46 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-11-04 21:31:52 | Re: how i can restrict databaseusers ? |
Previous Message | Scott Marlowe | 2008-11-04 18:48:35 | Re: rebellious postgres process |