On Thu, May  8, 2025 at 12:47:22PM +1200, David Rowley wrote:
> On Thu, 8 May 2025 at 12:36, Bruce Momjian <br...@momjian.us> wrote:
> > +Change pg_backend_memory_contexts.level and 
> > pg_log_backend_memory_contexts()() to be one-based (Melih Mutlu, Fujii 
> > Masao)
> 
> There's an extra set of parentheses on that function name. There's
> also an inconsistency between the commit link you added and the author
> you added. You've put the author of 706cbed3510 but the commit link
> contains d9e03864b.

Ah, I see those now.  It was two commits.  For some reason the edits are
hard for me;  applied patch attached.

-- 
  Bruce Momjian  <br...@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.
diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml
index 5e23688e9b8..4f45c90d7d2 100644
--- a/doc/src/sgml/release-18.sgml
+++ b/doc/src/sgml/release-18.sgml
@@ -174,14 +174,18 @@ This is now longer needed since pg_backend_memory_contexts.path was added.
 Author: David Rowley <drow...@postgresql.org>
 2024-07-25 [32d3ed816] Add path column to pg_backend_memory_contexts view
 Author: David Rowley <drow...@postgresql.org>
-2025-04-18 [d9e03864b] Make levels 1-based in pg_log_backend_memory_contexts()
+2025-04-18 [d9e03864b] Make levels 1-based in
+pg_log_backend_memory_contexts()
+Author: Fujii Masao <fu...@postgresql.org>
+2025-04-21 [706cbed35] doc: Fix memory context level in pg_log_backend_memory_c
 -->
 
 <listitem>
 <para>
-Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts()() to be one-based (Melih Mutlu, Fujii Masao)
+Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao)
 <ulink url="&commit_baseurl;32d3ed816">&sect;</ulink>
 <ulink url="&commit_baseurl;d9e03864b">&sect;</ulink>
+<ulink url="&commit_baseurl;706cbed35">&sect;</ulink>
 </para>
 
 <para>

Reply via email to