Re: Add missing stats_reset column to pg_stat_database_conflicts view - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Add missing stats_reset column to pg_stat_database_conflicts view
Date
Msg-id CAHGQGwEeGUQtj7TOznM2_O2uV-g6iOa1UBBTBfyugJ-nSoS89Q@mail.gmail.com
Whole thread Raw
In response to Re: Add missing stats_reset column to pg_stat_database_conflicts view  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Add missing stats_reset column to pg_stat_database_conflicts view
List pgsql-hackers
On Tue, Mar 10, 2026 at 8:33 AM Sami Imseih <samimseih@gmail.com> wrote:
>
> > The attached patch adds pg_stat_get_db_stat_reset_time() to fix this
> > inconsistency.
> >
> > Please let me know your thoughts.
>
> This view was introduced 15 years ago, and surprisingly this is the
> first complaint about this. I am also not very surprised.
>
> I also noticed that pg_statio_all_sequences does not have a reset
> column. We should fix this one also. What do you think?

+1

Also it might be better to update the docs together so that the description of
pg_stat_reset_single_table_counters mentions sequences in addition to
tables and indexes.

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Shinya Kato
Date:
Subject: Re: pg_stat_replication.*_lag sometimes shows NULL during active replication
Next
From: "zengman"
Date:
Subject: Remove redundant cast in gindesc.c