Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) - Mailing list pgsql-bugs

From Maxim Boguk
Subject Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Date
Msg-id CAK-MWwSK5AUneiF5zyDvc_9pO4ZNTT_G45ZQG1AD+n55s2zzTg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Maxim Boguk <maxim.boguk@gmail.com>)
Responses Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
List pgsql-bugs
>>So yes,  pgstat_send_inquiry definitely issued by autovacuum launcher.
>>Now question why EVERY pgstat_send_inquiry request from autovacuum leads
to the 1-2 full >>pgstat.stat rewrite on idle server?

Just another theory
It happens exactly because the full idle server so no other activity which
could provide some changes to pgstat.tmp file timestamp.

May be it could be good idea to update timestamp of pgstat.tmp file on
every PgstatCollectorMain iteration if nothing had been received from stat
socket?
Or alternatively internally track the timestamp of the last update received
from stat socket, and skip file rewrite step if nothing had been received
since last full rewrite?

Kind Regards,
Maksym

pgsql-bugs by date:

Previous
From: Maxim Boguk
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)