| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | 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-24 05:33:29 |
| Message-ID: | 20220324053329.edxicqcpk7aytmtp@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-24 06:27:48 +0100, Laurenz Albe wrote:
> On Wed, 2022-03-23 at 17:55 -0700, Andres Freund wrote:
> > Starting with the below commit, pg_stat_reset_single_function_counters,
> > pg_stat_reset_single_table_counters don't just reset the stats for the
> > individual function, but also set pg_stat_database.stats_reset.
>
> I see the point in the fine-grained reset, but I am -1 on having that
> reset "pg_stat_database.stats_reset". That would make the timestamp
> mostly useless.
Just to be clear - that's the current and long-time behaviour.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-03-24 06:00:58 | Re: shared-memory based stats collector - v67 |
| Previous Message | Dilip Kumar | 2022-03-24 05:28:47 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |