postgres.git / summary / log / commit / refs

commit    bbd4951b73ec5ba4356133140da19cf378a796fd
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Thu Mar 24 11:56:31 2022 +0000

    doc: Improve postgres command for shared_memory_size_in_huge_pages
    
    The command used in the documentation to retrieve the value of the
    runtime-computed GUC shared_memory_size_in_huge_pages would also show to
    the user all the log messages generated by the postmaster before and
    after printing the wanted value.  This can be confusing, as the wanted
    result could be masked with a lot of noise.
    
    One way to avoid those log messages is to use something like "-c
    log_min_messages=fatal" in the command (my idea, but that's not common
    knowledge).  Rather than mentioning this option, suffix the command with
    a redirection of stderr to /dev/null, which is the stream location where
    the logs show up.  This is enough to show only the GUC value to the
    user when copy-pasting the command.
    
    Reported-by: Magnus Hagander
    Author: Nathan Bossart
    Discussion: https://postgr.es/m/20220314173417.GA1020555@nathanxps13


 doc/src/sgml/runtime.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index ffb0b6f287b..3a463f12d75 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1448,7 +1448,7 @@ export PG_OOM_ADJUST_VALUE=0
     server must be shut down to view this runtime-computed parameter.
     This might look like:
 <programlisting>
-$ <userinput>postgres -D $PGDATA -C shared_memory_size_in_huge_pages</userinput>
+$ <userinput>postgres -D $PGDATA -C shared_memory_size_in_huge_pages 2> /dev/null</userinput>
 3170
 $ <userinput>grep ^Hugepagesize /proc/meminfo</userinput>
 Hugepagesize:       2048 kB


[parent: 127aea2a65cd]