From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: configurability of OOM killer |
Date: | 2008-02-04 22:01:44 |
Message-ID: | 1202162504.10057.806.camel@dogma.ljc.laika.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2008-02-04 at 16:48 -0500, Tom Lane wrote:
> Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> writes:
> > 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?
>
> Certainly that would help, and it might be an easier sell to the kernel
> hackers: instead of arguing "this policy is foolish", we only have to
> say "your VM accounting is wildly inaccurate". We'd still end up with a
> postmaster at more risk than we'd like, but at least not at dozens of
> times more risk than any backend.
>
I agree completely, and that's exactly the argument I tried to make on
LKML a year ago:
http://kerneltrap.org/mailarchive/linux-kernel/2007/2/12/54202
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-04 22:06:22 | Re: Why are we waiting? |
Previous Message | Simon Riggs | 2008-02-04 22:00:23 | Re: configurability of OOM killer |