Horton

Re: Add missing stats_reset column to pg_stat_database_conflicts view

Chao Li <li.evan.chao@gmail.com>

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

> 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 still saw (SELECT current_database()) in v7. Does it have any special meaning than just current_database()?

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

Commits

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

  2. Add stats_reset column to pg_stat_database_conflicts.