Re: Add missing stats_reset column to pg_stat_database_conflicts view

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(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-06 04:22:34
Message-ID: CAHGQGwFpdUVUtwz=GMZN+HcbL6UACb1V9BgF7j+=59deN9uQjA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ls7777 2026-04-06 04:34:08 Re: Patch for migration of the pg_commit_ts directory
Previous Message Richard Guo 2026-04-06 03:40:25 Re: Asynchronous MergeAppend