Re: Postgres stats collector showing high disk I/O

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Justin Pasher <justinp(at)newmediagateway(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgres stats collector showing high disk I/O
Date: 2010-05-20 22:11:44
Message-ID: 9605.1274393504@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Excerpts from Justin Pasher's message of jue may 20 16:10:53 -0400 2010:
>> Whenever I clear out the stats for all of the databases, the file
>> shrinks down to <1MB. However, it only takes about a day for it to get
>> back up to ~18MB and then the stats collector process start the heavy
>> disk writing again.

> I wonder if we should make pgstats write one file per database (plus one
> for shared objects), instead of keeping everything in a single file.
> That would reduce the need for reading and writing so much.

Well, the real problem here is the OP is running 8.1, so he isn't
getting the benefit of any of the subsequent changes to reduce the
stats file I/O. I suspect the bloat also comes from a
subsequently-fixed bug, but not totally sure about that yet.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-05-20 22:36:48 Re: postgres startup failure
Previous Message Matt Bartolome 2010-05-20 22:07:10 Re: postgres startup failure

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-05-20 22:21:09 Re: Unexpected data beyond EOF during heavy writes
Previous Message Rosser Schwarz 2010-05-20 21:38:41 Re: Unexpected data beyond EOF during heavy writes