Re: PG 18 release notes draft committed - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: PG 18 release notes draft committed
Date
Msg-id aBjGlj+Yi++fVRQt@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to PG 18 release notes draft committed  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 18 release notes draft committed
Re: PG 18 release notes draft committed
List pgsql-hackers
Hi,

On Thu, May 01, 2025 at 10:44:50PM -0400, Bruce Momjian wrote:
> I have committd the first draft of the PG 18 release notes. 

Thanks for working on this!

> You can see the most current HTML-built version here:
> 
>     https://momjian.us/pgsql_docs/release-18.html


I have one comment related to "per backend" statistics.

We have this:

"
Add per-backend I/O statistics reporting (Bertrand Drouvot)

The statistics are accessed via pg_stat_get_backend_io(). Per-backend statistics can be cleared via
pg_stat_reset_backend_stats().
 
"

and

"
Add function pg_stat_get_backend_wal() to return per-backend WAL statistics (Bertrand Drouvot) 
"

I think that we could mention pg_stat_reset_backend_stats() in both case, something
like:

A.

"Per-backend I/O statistics can be cleared via pg_stat_reset_backend_stats()"

and

"Per-backend WAL statistics can be cleared via pg_stat_reset_backend_stats()"

for consitency.

Or:

B.  mention pg_stat_reset_backend_stats() "separately" just saying:

"
Per-backend statistics can be cleared via pg_stat_reset_backend_stats()
"

and get rid of the mention in "per-backend I/O statistics".

I'd be tempted to vote for B (so that pg_stat_reset_backend_stats() is introduced
separately): thoughts?

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Fix a race condition in ConditionVariableTimedSleep()
Next
From: Tom Lane
Date:
Subject: Re: PATCH: pg_dump to support "on conflict do update"