| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: configurability of OOM killer |
| Date: | 2008-02-04 21:31:53 |
| Message-ID: | 47A78449.4000104@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Yeah, the only way to improve the OOM problem would be to harass the
> Linux developers to tweak badness() so that it considers the postmaster
> to be an essential process rather than the one to preferentially kill.
Wouldn't the more general rule that Jeff Davis pointed out upstream
make more sense?
That shared memory of the children should not be added to the size
of the parent process multiple times regardless of if something's
an essential process or not. Since those bytes are shared, it
seems such bytes should only be added to the badness once, no?
(assuming I understood Jeff correctly)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2008-02-04 21:40:49 | Re: configurability of OOM killer |
| Previous Message | 0123 zyxw | 2008-02-04 21:26:06 | Re: FW: bitemporal functionality for PostgreSQL |