| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Subject: | Re: pg_stat_reset_single_*_counters vs pg_stat_database.stats_reset |
| Date: | 2022-03-30 20:39:27 |
| Message-ID: | 20220330203927.djyc3ifjgyao7lv7@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-30 12:29:51 -0700, David G. Johnston wrote:
> On Wednesday, March 30, 2022, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > My current proposal is to just have two reset times. One for the contents
> > of
> > pg_stat_database (i.e. not affected by pg_stat_reset_single_*_counters()),
> > and
> > one for stats within the entire database.
> What IS it affected by? And does whatever affects it affect anything else?
pg_stat_reset() resets the current database's stats. That includes the
database's row in pg_stat_database and all table and function stats.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-30 20:44:24 | Re: Higher level questions around shared memory stats |
| Previous Message | James Coleman | 2022-03-30 20:33:18 | Re: Correct docs re: rewriting indexes when table rewrite is skipped |