Re: Add missing stats_reset column to pg_stat_database_conflicts view

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add missing stats_reset column to pg_stat_database_conflicts view
Date: 2026-04-07 03:58:08
Message-ID: 69673789-9B93-496F-968E-C00F19A122CA@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Apr 6, 2026, at 12:22, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Mon, Mar 16, 2026 at 11:11 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jie wang 2026-04-07 03:59:14 Re: Return DSA area for hash table from GetNamedDSHash()
Previous Message jie wang 2026-04-07 03:55:15 Re: Add errdetail() with PID and UID about source of termination signal