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

From Kirill Reshke
Subject Re: Add missing stats_reset column to pg_stat_database_conflicts view
Date
Msg-id CALdSSPi4apueVqgnJEZqpy6O0HSEPUiUzf=vTLPPijsQLob2Eg@mail.gmail.com
Whole thread Raw
In response to Re: Add missing stats_reset column to pg_stat_database_conflicts view  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Add missing stats_reset column to pg_stat_database_conflicts view
List pgsql-hackers
On Tue, 10 Mar 2026 at 06:17, Fujii Masao <masao.fujii@gmail.com> wrote:
>
> 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
>

Well, it looks like there are not so many users of this view. Anyway,
+1 on change.
This also need catversion bump

--
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Jim Jones
Date:
Subject: Re: ALTER TABLE: warn when actions do not recurse to partitions
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD