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: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(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-03-13 08:46:54
Message-ID: 126F5EBD-16EB-4786-8A65-8D1BCC0F20D7@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mar 13, 2026, at 04:39, Sami Imseih <samimseih(at)gmail(dot)com> wrote:
>
>> I also made some cosmetic indentation fixes in the docs.
>> The v6 patch is attached.
>
> Just one more minor comment fix I noticed.
>
> "Test that reset works for pg_stat_database"
>
> to:
>
> "Test that reset works for pg_stat_database and pg_stat_database_conflicts"
>
> --
> Sami
> <v7-0001-Add-stats_reset-column-to-pg_stat_database_confli.patch>

I still saw (SELECT current_database()) in v7. Does it have any special meaning than just current_database()?

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2026-03-13 09:08:08 Re: Make copyObject work in C++
Previous Message Viktor Holmberg 2026-03-13 08:43:31 Re: support fast default for domain with constraints