postgres.git / summary / log / commit / refs

commit    a0d87e2a92ea37d136b5ce69af2e8cd7c6127a35
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue Aug 23 13:41:37 2022 +0000
First released in: 16.0, 10.23, 11.18, 12.13, 13.9, 14.6, 15.0

    Doc: prefer sysctl to /proc/sys in docs and comments.
    
    sysctl is more portable than Linux's /proc/sys file tree, and
    often easier to use too.  That's why most of our docs refer to
    sysctl when talking about how to adjust kernel parameters.
    Bring the few stragglers into line.
    
    Discussion: https://postgr.es/m/361175.1661187463@sss.pgh.pa.us


 doc/src/sgml/runtime.sgml           | 11 ++++++-----
 src/backend/postmaster/postmaster.c |  2 +-
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 66dacaeb422..d0632f2d08a 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1302,11 +1302,12 @@ default:\
     <itemizedlist>
      <listitem>
       <para>
-      On <productname>Linux</productname>
-      <filename>/proc/sys/fs/file-max</filename> determines the
-      maximum number of open files that the kernel will support.  It can
-      be changed by writing a different number into the file or by
-      adding an assignment in <filename>/etc/sysctl.conf</filename>.
+      On <productname>Linux</productname> the kernel parameter
+      <varname>fs.file-max</varname> determines the maximum number of open
+      files that the kernel will support.  It can be changed with
+      <literal>sysctl -w fs.file-max=<replaceable>N</replaceable></literal>.
+      To make the setting persist across reboots, add an assignment
+      in <filename>/etc/sysctl.conf</filename>.
       The maximum limit of files per process is fixed at the time the
       kernel is compiled; see
       <filename>/usr/src/linux/Documentation/proc.txt</filename> for
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
index 661b2d037f2..ddf553b85b9 100644
--- a/src/backend/postmaster/postmaster.c
+++ b/src/backend/postmaster/postmaster.c
@@ -4876,7 +4876,7 @@ SubPostmasterMain(int argc, char *argv[])
 	 * If testing EXEC_BACKEND on Linux, you should run this as root before
 	 * starting the postmaster:
 	 *
-	 * echo 0 >/proc/sys/kernel/randomize_va_space
+	 * sysctl -w kernel.randomize_va_space=0
 	 *
 	 * This prevents using randomized stack and code addresses that cause the
 	 * child process's memory map to be different from the parent's, making it


[parent: 6b50433e865e]