Request a Demo
Home   >   mailing lists

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 CAHGQGwG2OpV-Z-8d9K1owosKhsDKO2kiJVvvkEzWoOMp3NzAcQ@mail.gmail.com
Whole thread
In response to Re: Add missing stats_reset column to pg_stat_database_conflicts view  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Add missing stats_reset column to pg_stat_database_conflicts view
List pgsql-hackers
Tree view 
On Fri, Mar 13, 2026 at 5:47 PM Chao Li <li.evan.chao@gmail.com> wrote:
>
>
>
> > On Mar 13, 2026, at 04:39, Sami Imseih <samimseih@gmail.com> wrote:
> >
> >> I also made some cosmetic indentation fixes in the docs.
> >> The v6 patch is attached.
> >
> > Just one more minor comment fix I noticed.
> >
> > "Test that reset works for pg_stat_database"
> >
> > to:
> >
> > "Test that reset works for pg_stat_database and pg_stat_database_conflicts"
> >
> > --
> > Sami
> > <v7-0001-Add-stats_reset-column-to-pg_stat_database_confli.patch>

I've pushed the patch. Thanks!


> I still saw (SELECT current_database()) in v7. Does it have any special meaning than just current_database()?

No. I think it was used by the patch simply because the existing tests
for stats reset already use it.

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Add --extra-dependencies and immediate data dumping for pg_dump/pg_upgrade
Next
From: Peter Eisentraut
Date:
Subject: Re: tid_blockno() and tid_offset() accessor functions