Re: Postgres stats collector showing high disk I/O - Mailing list pgsql-general

From Tom Lane
Subject Re: Postgres stats collector showing high disk I/O
Date
Msg-id 18564.1272062283@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres stats collector showing high disk I/O  (Justin Pasher <justinp@newmediagateway.com>)
List pgsql-general
Justin Pasher <justinp@newmediagateway.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

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Postgres stats collector showing high disk I/O
Next
From: Justin Pasher
Date:
Subject: Re: Postgres stats collector showing high disk I/O