Looks like that was the problem - got a day under the belt now with the
8.2.4 rev and all is back to normal.
Karl Denninger (karl@denninger.net)
http://www.denninger.net
Karl Denninger wrote:
> Aha!
>
> BIG difference. I won't know for sure until the biz day tomorrow but
> the "first blush" look is that it makes a HUGE difference in system
> load, and I no longer have the stats collector process on the top of
> the "top" list......
>
> Karl Denninger (karl@denninger.net)
> http://www.denninger.net
>
>
>
>
> Tom Lane wrote:
>> Karl Denninger <karl@denninger.net> writes:
>>
>>> Hmmmmm..... now that's interesting. Stats collector IS accumulating
>>> quite a bit of runtime..... me thinks its time to go grab 8.2.4.
>>>
>>
>> I think Merlin might have nailed it --- the "stats collector bug" is
>> that it tries to write out the stats file way more often than it
>> should. So any excessive userland CPU time you see is just the tip
>> of the iceberg compared to the system and I/O costs incurred.
>>
>> regards, tom lane
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 1: if posting/reading through Usenet, please send an appropriate
>> subscribe-nomail command to majordomo@postgresql.org so that your
>> message can get through to the mailing list cleanly
>>
>>
>> %SPAMBLOCK-SYS: Matched [hub.org+], message ok
>>
>
>
> %SPAMBLOCK-SYS: Matched [@postgresql.org+], message ok
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>
> %SPAMBLOCK-SYS: Matched [hub.org+], message ok
%SPAMBLOCK-SYS: Matched [@postgresql.org+], message ok
