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

Re: Stats collector on rampage (8.2.3)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: hubert depesz lubaczewski <depesz(at)depesz(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stats collector on rampage (8.2.3)
Date: 2007-10-29 09:47:51
Message-ID: 4725AC47.4000001@hagander.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Gaetano Mendola wrote:
> hubert depesz lubaczewski wrote:
>> On Mon, Oct 29, 2007 at 09:52:24AM +0100, Gaetano Mendola wrote:
>>> it seems that the stats collector on my box is using more CPU than
>>> it did in the past.
>> it's well known bug, and it was fixed in 8.2.4:
>> http://www.postgresql.org/docs/current/interactive/release-8-2-4.html
>> ...
>> Prevent the statistics collector from writing to disk too frequently
>> (Tom)
>> ...
> 
> I saw that, upgrading the DB at this very moment is not doable, killing
> that process will the postmaster respawn another one? BTW I discover that
> it was triggered by the time change due the daylight saving.

IIRC, it will. You need to change postgresql.conf and disable the stats
collector. If you do that, it won't be started.

Shouldn't be trigged by DST.

//Magnus

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-10-29 09:51:25
Subject: Re: Stats collector on rampage (8.2.3)
Previous:From: Gaetano MendolaDate: 2007-10-29 09:45:36
Subject: Re: Stats collector on rampage (8.2.3)

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