| From: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
| Date: | 2014-11-26 21:36:23 |
| Message-ID: | CAK-MWwSK5AUneiF5zyDvc_9pO4ZNTT_G45ZQG1AD+n55s2zzTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
>>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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-11-26 21:50:55 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
| Previous Message | Maxim Boguk | 2014-11-26 21:19:32 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-11-26 21:45:53 | Re: bug in json_to_record with arrays |
| Previous Message | Andrew Dunstan | 2014-11-26 21:34:50 | Re: bug in json_to_record with arrays |