From: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Reseting statistics counters |
Date: | 2013-12-06 23:31:40 |
Message-ID: | 52A25E5C.9090405@fuzzy.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 16.11.2013 20:49, Strahinja Kustudić wrote:
> Sorry for the late reply, but as far as I know when you run
> pg_stat_reset() you should always run analyze manually of the
> database to populate the statistics.
Why?
There are two kinds of stats in the database - stats used by the planner
(common column values, histograms, ...) and runtime stats. pg_stat_reset
only deals with the latter, it won't discard histograms or anything like
that.
And runnning analyze won't magically populate the runtime stats - for
example how could it populate number of sequential/index scans or the
timestamp of the last autovacuum?
The only thing that may be influenced by this is autovacuum, because
this will remove timestamp of the last run on the tables, number of
deleted/dead tuples etc. So it will be invoked on all tables, collecting
this info.
regards
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2013-12-06 23:59:26 | Re: WAL + SSD = slow inserts? |
Previous Message | Richard Huxton | 2013-12-06 18:37:13 | Re: postgres performance |