public inbox for [email protected]
help / color / mirror / Atom feedFrom: Fujii Masao <[email protected]>
To: Chao Li <[email protected]>
Cc: Sami Imseih <[email protected]>
Cc: shihao zhong <[email protected]>
Cc: Kirill Reshke <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Add missing stats_reset column to pg_stat_database_conflicts view
Date: Fri, 13 Mar 2026 22:25:00 +0900
Message-ID: <CAHGQGwG2OpV-Z-8d9K1owosKhsDKO2kiJVvvkEzWoOMp3NzAcQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAGRkXqS98OebEWjax99_LVAECsxCB8i=BfsdAL34i-5QHfwyOQ@mail.gmail.com>
<CAA5RZ0vSjCEAuKXhxacnp0ftrYkf9QRcyPK-AvTi_otFVDWphA@mail.gmail.com>
<CAHGQGwEeGUQtj7TOznM2_O2uV-g6iOa1UBBTBfyugJ-nSoS89Q@mail.gmail.com>
<CALdSSPi4apueVqgnJEZqpy6O0HSEPUiUzf=vTLPPijsQLob2Eg@mail.gmail.com>
<CAGRkXqQ0qBHTcD=UZ7_GTLsgn+W-=1c8suMJ3yWZb2eP4m0fBg@mail.gmail.com>
<CAA5RZ0ta3y==2AStFyo-SYyJ2ztd3ZiurN1HQR9gzDTKVtgUDg@mail.gmail.com>
<CAGRkXqRVDuhXNCvQ=j-+5KCu+Gcar_h5OeHTaMaVKF-FLV2YvQ@mail.gmail.com>
<CAHGQGwHaHnRrz9hqpDdn984mqToJDdkjMRVvEXXgFwCnXJb89Q@mail.gmail.com>
<[email protected]>
<CAA5RZ0uStx0cWUCNPDPhBprAVmcdOX-uuKd9B_W9qLa6Tsp46w@mail.gmail.com>
<CAHGQGwF3=y-j5LxHdXtthEsmJYY5U6WtcAsgwbestfCtNvvuaw@mail.gmail.com>
<CAA5RZ0uy79o0vr2=LeRHS2MZ7V6HGOCsys6YAbmmj3BW8tnziw@mail.gmail.com>
<[email protected]>
On Fri, Mar 13, 2026 at 5:47 PM Chao Li <[email protected]> wrote:
>
>
>
> > On Mar 13, 2026, at 04:39, Sami Imseih <[email protected]> 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've pushed the patch. Thanks!
> I still saw (SELECT current_database()) in v7. Does it have any special meaning than just current_database()?
No. I think it was used by the patch simply because the existing tests
for stats reset already use it.
Regards,
--
Fujii Masao
view thread (24+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Add missing stats_reset column to pg_stat_database_conflicts view
In-Reply-To: <CAHGQGwG2OpV-Z-8d9K1owosKhsDKO2kiJVvvkEzWoOMp3NzAcQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox