From: Peter Eisentraut <peter_e@gmx.net>
Date: Tue, 8 Nov 2011 04:49:50 +0000 (+0200)
Subject: -DLINUX_OOM_ADJ=0 should be in CPPFLAGS, not CFLAGS
X-Git-Tag: REL9_2_BETA1~857
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6477d66780df0682e36e676fd746356bb23bf7ce;p=postgresql

-DLINUX_OOM_ADJ=0 should be in CPPFLAGS, not CFLAGS
---

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 86499c67ac..08f9fd0b20 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1342,7 +1342,7 @@ echo -17 > /proc/self/oom_adj
     Note that this action must be done as root, or it will have no effect;
     so a root-owned startup script is the easiest place to do it.  If you
     do this, you may also wish to build <productname>PostgreSQL</>
-    with <literal>-DLINUX_OOM_ADJ=0</> added to <varname>CFLAGS</>.
+    with <literal>-DLINUX_OOM_ADJ=0</> added to <varname>CPPFLAGS</>.
     That will cause postmaster child processes to run with the normal
     <varname>oom_adj</> value of zero, so that the OOM killer can still
     target them at need.