Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)

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 23:13:52
Message-ID: CAK-MWwQ2ZCW3+8UiMAdtLc6+YHph_CS3R8fVeLAFkfWdC08VFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

>
> 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/>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2014-11-26 23:21:42 Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Previous Message Maxim Boguk 2014-11-26 23:01:32 Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2014-11-26 23:21:42 Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Previous Message Maxim Boguk 2014-11-26 23:01:32 Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)