-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 86499c67ac58459261e22616083eaba0cb3984f9..08f9fd0b20f57e8715d141f700e5140128c71c67 100644 (file)
--- 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 PostgreSQL
-    with -DLINUX_OOM_ADJ=0 added to CFLAGS.
+    with -DLINUX_OOM_ADJ=0 added to CPPFLAGS.
     That will cause postmaster child processes to run with the normal
     oom_adj value of zero, so that the OOM killer can still
     target them at need.