public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Yugo Nagata <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: First draft of PG 17 release notes
Date: Fri, 16 Aug 2024 13:02:19 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Fri, Jul 26, 2024 at 01:22:24PM +0900, Yugo Nagata wrote:
> I found the following in the release notes:
>
> Change file boundary handling of two WAL file name functions
> (Kyotaro Horiguchi, Andres Freund, Bruce Momjian)
>
> The functions pg_walfile_name() and pg_walfile_name_offset() used to report the previous
> LSN segment number when the LSN was on a file segment boundary; it now returns the LSN segment.
>
> It might be trivial, but, reading the associated commit message , I think it would be more explicit
> for users to rewrite the last statement to
>
> "it now returns the current LSN segment."
Agreed, applied patch attached. Sorry for the delay.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Attachments:
[text/x-diff] REL_17_STABLE.diff (589B, ../[email protected]/2-REL_17_STABLE.diff)
download | inline diff:
diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml
index dfbf8a74cd4..8a1e51f10d6 100644
--- a/doc/src/sgml/release-17.sgml
+++ b/doc/src/sgml/release-17.sgml
@@ -176,7 +176,7 @@ Author: Bruce Momjian <[email protected]>
and <function>pg_walfile_name_offset()</function> used to report
the previous <acronym>LSN</acronym> segment number when the
<acronym>LSN</acronym> was on a file segment boundary; it now
- returns the <acronym>LSN</acronym> segment.
+ returns the current <acronym>LSN</acronym> segment.
</para>
</listitem>
view thread (146+ 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]
Subject: Re: First draft of PG 17 release notes
In-Reply-To: <[email protected]>
* 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