Request a Demo
Home   >   mailing lists

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

From Sami Imseih
Subject Re: Add missing stats_reset column to pg_stat_database_conflicts view
Date
Msg-id CAA5RZ0vSjCEAuKXhxacnp0ftrYkf9QRcyPK-AvTi_otFVDWphA@mail.gmail.com
Whole thread Raw
In response to Add missing stats_reset column to pg_stat_database_conflicts view  (shihao zhong <zhong950419@gmail.com>)
Responses Re: Add missing stats_reset column to pg_stat_database_conflicts view
List pgsql-hackers
Tree view 
> 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?

With regards to your attached patch, it's missing the doc changes.
but also the patch does not apply.

--
Sami Imseih
Amazon Web Services (AWS)

pgsql-hackers by date:

Previous
From: Gyan Sreejith
Date:
Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber
Next
From: Lukas Fittl
Date:
Subject: Re: Stack-based tracking of per-node WAL/buffer usage