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

Re: rebellious postgres process

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:46:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"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.

			regards, tom lane

In response to


pgsql-admin by date

Next:From: Scott MarloweDate: 2008-11-04 18:48:35
Subject: Re: rebellious postgres process
Previous:From: Scott MarloweDate: 2008-11-04 18:03:30
Subject: Re: rebellious postgres process

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