diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2011-11-08 06:49:50 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2011-11-08 06:51:01 +0200 |
| commit | 0ff319d20af757946f57719959172612d0ec75cc (patch) | |
| tree | fb2618c125124c26969315eea994d5406b050999 | |
| parent | d747a45b46139eb78c060e1f3c3ee4d3dc72db12 (diff) | |
-DLINUX_OOM_ADJ=0 should be in CPPFLAGS, not CFLAGS
| -rw-r--r-- | doc/src/sgml/runtime.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index d11c5bc8cfc..dc474a6c345 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1291,7 +1291,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. |