Horton

Re: Add missing stats_reset column to pg_stat_database_conflicts view

Fujii Masao <masao.fujii@gmail.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@gmail.com>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>, shihao zhong <zhong950419@gmail.com>, Kirill Reshke <reshkekirill@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-03-13T13:25:00Z
Lists: pgsql-hackers 
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

Commits

  1. Simplify redundant current_database() subqueries in stats.sql regression test

  2. Add stats_reset column to pg_stat_database_conflicts.