| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Should the docs have a warning about pg_stat_reset()? |
| Date: | 2019-04-11 01:49:06 |
| Message-ID: | CAKJS1f92xUWun6tarsA8iioE1H-_a=67MkKZLf663Ywgf2_=zQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 11 Apr 2019 at 06:52, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> OK, let me step back. Why are people resetting the statistics
> regularly? Based on that purpose, does it make sense to clear the
> stats that effect autovacuum?
I can't speak for everyone, but once upon a time when I first started
using PostgreSQL, to monitor the application's use of the database I
recorded the output of pg_stat_user_tables once per day and then reset
the statistics. It was useful to know the number of inserted tuples,
seq scans, index scans etc so I could understand the load on the
database better. Of course, nowadays with LEAD()/LAG() it's pretty
easy to find the difference from the previous day. I'd have done it
differently if those had existed back then.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Iwata, Aya | 2019-04-11 02:10:24 | RE: Contribution to Perldoc for TestLib module in Postgres |
| Previous Message | Stephen Frost | 2019-04-11 01:47:01 | Re: [PATCH v20] GSSAPI encryption support |