| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: configurability of OOM killer |
| Date: | 2008-02-02 00:08:24 |
| Message-ID: | 18162.1201910904@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> This page
> http://linux-mm.org/OOM_Killer
Egad. Whoever thought *this* was a good idea should be taken out
and shot:
The independent memory size of any child (except a kernel thread) is added to the score:
/*
* Processes which fork a lot of child processes are likely
* a good choice. We add the vmsize of the childs if they
* have an own mm. This prevents forking servers to flood the
* machine with an endless amount of childs
*/
In other words, server daemons are preferentially killed, and the parent
will *always* get zapped in place of its child (since the child cannot
have a higher score). No wonder we have to turn off OOM kill.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-02-02 00:36:54 | Re: configurability of OOM killer |
| Previous Message | Tom Lane | 2008-02-01 23:56:56 | Re: <IDLE> and waiting |