Re: Postgres stats collector showing high disk I/O

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pasher <justinp(at)newmediagateway(dot)com>
Cc: depesz(at)depesz(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres stats collector showing high disk I/O
Date: 2010-04-23 22:38:03
Message-ID: 18564.1272062283@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Justin Pasher <justinp(at)newmediagateway(dot)com> writes:
> Agh... I used pg_stats_reset (with an s) when searching for it. I ran
> the function and it returned true, but the stats file only shrunk by
> ~100k (still over 18MB total). Is there something else I need to do?

pg_stat_reset only resets the data for the current database (the one
you issue it in). Apparently most of your bloat is for some other
database(s).

If you've got a whole lot of databases, a possibly less painful
alternative to zapping them one at a time is to stop the server,
manually remove the stats file, start the server.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Justin Pasher 2010-04-23 22:46:16 Re: Postgres stats collector showing high disk I/O
Previous Message Alvaro Herrera 2010-04-23 22:28:03 Re: Postgres stats collector showing high disk I/O

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2010-04-23 22:39:48 Re: testing HS/SR - 1 vs 2 performance
Previous Message Tom Lane 2010-04-23 22:30:00 Re: recovery_connections cannot start (was Re: master in standby mode croaks)