Re: Add missing stats_reset column to pg_stat_database_conflicts view - Mailing list pgsql-hackers

From Chao Li
Subject Re: Add missing stats_reset column to pg_stat_database_conflicts view
Date
Msg-id 69673789-9B93-496F-968E-C00F19A122CA@gmail.com
Whole thread Raw
In response to Re: Add missing stats_reset column to pg_stat_database_conflicts view  (Fujii Masao <masao.fujii@gmail.com>)
List 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
thatreplaces 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/







pgsql-hackers by date:

Previous
From: jie wang
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal
Next
From: jie wang
Date:
Subject: Re: Return DSA area for hash table from GetNamedDSHash()