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

Re: rebellious postgres process

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Laszlo Nagy" <gandalf(at)shopzeus(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: rebellious postgres process
Date: 2008-11-04 18:03:30
Message-ID: dcc563d10811041003u2100bb10v11e90763f12de58f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Tue, Nov 4, 2008 at 8:48 AM, Laszlo Nagy <gandalf(at)shopzeus(dot)com> wrote:
> Tom Lane wrote:
>>
>> Huh, that's weird.  We've fixed some bugs in the past that led the stats
>> collector to consume excessive CPU --- but that was all pre-8.3.
>>
>
> 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.

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2008-11-04 18:46:00
Subject: Re: rebellious postgres process
Previous:From: David FetterDate: 2008-11-04 16:11:01
Subject: Re: epqa; postgres performance optimizer support tool;opensource.

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