Re: pg_stat_reset_single_*_counters vs pg_stat_database.stats_reset - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pg_stat_reset_single_*_counters vs pg_stat_database.stats_reset
Date
Msg-id 20220324053329.edxicqcpk7aytmtp@alap3.anarazel.de
Whole thread Raw
In response to Re: pg_stat_reset_single_*_counters vs pg_stat_database.stats_reset  (Laurenz Albe <laurenz.albe@cybertec.at>)
List 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



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: shared-memory based stats collector - v67