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: Fujii Masao <masao.fujii@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-04-07T03:58:08Z
Lists: pgsql-hackers 

> On Apr 6, 2026, at 12:22, Fujii Masao <masao.fujii@gmail.com> wrote:
> 
> On Mon, Mar 16, 2026 at 11:11 AM Chao Li <li.evan.chao@gmail.com> wrote:
>> I searched through the test scripts, and it looks like only stats.sql uses this pattern. So I attached a small patch that replaces all (SELECT current_database()) with current_database().
> 
> OK, I've pushed the patch. Thanks!
> 
> Regards,
> 
> -- 
> Fujii Masao

Thank you very much for pushing.

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.