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 CAHGQGwFpdUVUtwz=GMZN+HcbL6UACb1V9BgF7j+=59deN9uQjA@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
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
thatreplaces all (SELECT current_database()) with current_database(). 

OK, I've pushed the patch. Thanks!

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Asynchronous MergeAppend
Next
From: Michael Paquier
Date:
Subject: Re: Adding locks statistics