Skip site navigation (1) Skip section navigation (2)

Re: rebellious postgres process

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Laszlo Nagy" <gandalf(at)shopzeus(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: rebellious postgres process
Date: 2008-11-04 18:48:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Tue, Nov 4, 2008 at 11:46 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
>> On Tue, Nov 4, 2008 at 8:48 AM, Laszlo Nagy <gandalf(at)shopzeus(dot)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.

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

In response to


pgsql-admin by date

Next:From: Tom LaneDate: 2008-11-04 18:54:52
Subject: Re: rebellious postgres process
Previous:From: Tom LaneDate: 2008-11-04 18:46:00
Subject: Re: rebellious postgres process

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group