| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| 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:28:03 |
| Message-ID: | 20100423222803.GC2859@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Justin Pasher wrote:
> 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? Does this mean the file is mostly bloated with bogus
> data that it can't "reset"? I'm guessing I should just try to delete
> the file outright?
Err, yeah, pg_stat_reset only resets the stats for the current database.
You need to reset for all databases, or alternatively, shut down the
server, remove the file, and restart
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-04-23 22:38:03 | Re: Postgres stats collector showing high disk I/O |
| Previous Message | Justin Pasher | 2010-04-23 22:06:04 | Re: Postgres stats collector showing high disk I/O |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-04-23 22:30:00 | Re: recovery_connections cannot start (was Re: master in standby mode croaks) |
| Previous Message | Tom Lane | 2010-04-23 22:24:46 | Re: [HACKERS] Re: pgsql: Make CheckRequiredParameterValues() depend upon correct |