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 126F5EBD-16EB-4786-8A65-8D1BCC0F20D7@gmail.com
Whole thread Raw
In response to Re: Add missing stats_reset column to pg_stat_database_conflicts view  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Add missing stats_reset column to pg_stat_database_conflicts view
List pgsql-hackers

> On Mar 13, 2026, at 04:39, Sami Imseih <samimseih@gmail.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/







pgsql-hackers by date:

Previous
From: Viktor Holmberg
Date:
Subject: Re: support fast default for domain with constraints
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: Make copyObject work in C++