Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sf0LK-00Fgs1-2W for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Aug 2024 17:02:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sf0LI-006dn6-OD for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Aug 2024 17:02:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sf0LI-006dmx-EW for pgsql-hackers@lists.postgresql.org; Fri, 16 Aug 2024 17:02:24 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sf0LF-00552q-EW for pgsql-hackers@postgresql.org; Fri, 16 Aug 2024 17:02:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=a0qiKX0WnZikJ140o4EZnbie9ku5lRTZsjiNk3LziS8=; b=g5Xbf yd8a4UHICwj7qwynpSn433fzZj1yCFVnJZfWetZJBAJ3JADytBN3wTB/XdW34+f3kcODA5IADLPaR hKE4ka7wbGFtcgcNgKZoPqHtlC7QyNgB1iY10V4EMxqaftwbKFMigd4SUklFD4pkjvBafqL4FECSn rBKxcyZ8KhBkRkOjB3M8o75NGgNW68oKa1g1UatxoTmM6WCXdz4DUVPvwm0lGhJHI+EPSoUr7WH4j AjIz/i8pAbywzI0Dg5YN3F1J6oSfN1eMQtbNHNE0pH7sMQ8VMBA7SXfOZpT8wPzJ/kWbuGxJmnfQZ aE1il3Cvl2pndsnMz2Ya1SBFDr9sg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1sf0LD-003Xpy-1h; Fri, 16 Aug 2024 13:02:19 -0400 Date: Fri, 16 Aug 2024 13:02:19 -0400 From: Bruce Momjian To: Yugo Nagata Cc: PostgreSQL-development Subject: Re: First draft of PG 17 release notes Message-ID: References: <20240726132224.3a77e79c4e563125c451e865@sraoss.co.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="4kbp1j3O4WF2DBz1" Content-Disposition: inline In-Reply-To: <20240726132224.3a77e79c4e563125c451e865@sraoss.co.jp> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --4kbp1j3O4WF2DBz1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you. --4kbp1j3O4WF2DBz1 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="REL_17_STABLE.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 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. + returns the current LSN segment. --4kbp1j3O4WF2DBz1--