Thank you, everyone.
the point being to encourage its use before the server is running
as we don't want to allocate anything when tuning it.
I was mistaken and now understand that it needs to be run before the
server is running.
Another idea is to use the same wording as for num_os_semaphores in
runtime.sgml, like this:
WFM
I've fixed the patch and will register it in the CF.
Regards,
--
Yuki Seino
NTT DATA CORPORATION
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 2c4d5ef640..63669f2d2e 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1431,9 +1431,9 @@ export PG_OOM_ADJUST_VALUE=0
the operating system to provide enough huge pages of the desired size.
To determine the number of huge pages needed, use the
<command>postgres</command> command to see the value of
- <xref linkend="guc-shared-memory-size-in-huge-pages"/>. Note that the
- server must be shut down to view this runtime-computed parameter.
- This might look like:
+ <xref linkend="guc-shared-memory-size-in-huge-pages"/>. This parameter
+ can be viewed before starting the server with a <command>postgres</command>
+ command like:
<programlisting>
$ <userinput>postgres -D $PGDATA -C shared_memory_size_in_huge_pages</userinput>
3170
