From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
From: Palak Chaturvedi <palakchaturvedi2843@gmail.com>
Date: Mon, 14 Sep 2026 15:33:02 +0000
Subject: [PATCH] doc: update buffer resize documentation

- InitProcess()/InitProcessPhase2(): 'specifid' -> 'specified'
- func-admin.sgml: garbled paragraph in pg_resize_shared_buffers() docs
- config.sgml: quantify the memory max_shared_buffers reserves upfront
---
 doc/src/sgml/config.sgml          |    9 +++++----
 doc/src/sgml/func/func-admin.sgml |   11 +++++------
 src/backend/storage/lmgr/proc.c   |    2 +-
 3 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 8418af072f9..031a82c04da 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1844,9 +1844,6 @@ include_dir 'conf.d'
         other GUCS which use this GUCs value to set their defaults will not be
         changed. They may still require a server restart to consider new value.
        </para>
-
-       <para>
-       </para>
       </listitem>
      </varlistentry>
 
@@ -1875,7 +1872,11 @@ include_dir 'conf.d'
         memory required for the buffer lookup table and the array used to sort
         buffers during a checkpoint is allocated at the server start
         considering the largest buffer pool size allowed by this parameter.
-        <!-- TODO: Provide a numeric example of how much extra memory say max_shared_buffers = 1GB consume. -->
+        For example, with the default block size of 8kB,
+        <literal>max_shared_buffers = 1GB</literal> allows for 131072 buffers,
+        whose lookup table and sort array together occupy about 9.5MB,
+        regardless of the current value of
+        <varname>shared_buffers</varname>.
        </para>
 
        <para>
diff --git a/doc/src/sgml/func/func-admin.sgml b/doc/src/sgml/func/func-admin.sgml
index 2a621fff060..9d345c7ecaa 100644
--- a/doc/src/sgml/func/func-admin.sgml
+++ b/doc/src/sgml/func/func-admin.sgml
@@ -160,12 +160,11 @@ postgres=# SHOW shared_buffers; -- Step 5 (verification)
         pending to be applied.
        </para>
        <para>
-        <!-- TODO: Document behaviour when the function is called on platforms that do not support resizable shared memory -->
-    linkend="functions-admin-signal-table"/> send control signals to
-    other server processes.  Use of these functions is restricted to
-    superusers by default but access may be granted to others using
-    <command>GRANT</command>, with noted exceptions.
-   </para>
+        If <xref linkend="guc-have-resizable-shmem"/> is <literal>off</literal>,
+        this function reports an error instead of resizing the buffer pool, and
+        the pending value of <varname>shared_buffers</varname> takes effect only
+        after the server is restarted.
+       </para>
        </entry>
       </row>
      </tbody>
diff --git a/src/backend/storage/lmgr/proc.c b/src/backend/storage/lmgr/proc.c
index 8332bc0b252..92cfb37f660 100644
--- a/src/backend/storage/lmgr/proc.c
+++ b/src/backend/storage/lmgr/proc.c
@@ -798,7 +798,7 @@ InitAuxiliaryProcess(void)
 	 * callback above.
 	 *
 	 * We also call this function after ProcSignalInit() for the reasons
-	 * specifid there, but we need it here so that InitBufferManagerAccess()
+	 * specified there, but we need it here so that InitBufferManagerAccess()
 	 * can use the current buffer pool size.
 	 */
 	BufferManagerInitProc();
-- 
2.43.0