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-MWwQ2ZCW3+8UiMAdtLc6+YHph_CS3R8fVeLAFkfWdC08VFQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Tomas Vondra <tv@fuzzy.cz>)
Responses Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
>
> I'm not sure why this was not happening before, though ...
>
> Tomas
>
>
It not happened before because just few weeks ago development process had
been switched from single shared developer db to the private db's for each
developer (so amount of databases increased from few to 10).

PS: 10ms acceptable lag for autovacuum reading pgstat.tmp looks too strong
limitation for me.
I think it should be something like min(autovacuum_naptime/2,
PGSTAT_RETRY_DELAY)

--
Maxim Boguk
Senior Postgresql DBA
http://www.postgresql-consulting.ru/ <http://www.postgresql-consulting.com/>

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)