Re: configurability of OOM killer

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Florian Weimer <fweimer(at)bfk(dot)de>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: configurability of OOM killer
Date: 2008-02-02 20:01:41
Message-ID: 47A4CC25.8080501@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian G. Pflug wrote:
>
> Maybe we should just react equally brute-force, and just disable the
> OOM-Killer for the postmaster if we're running on linux. It seems that
> something like "echo -17 > /proc/<pid>/oom_adj" should do the trick.

That will protect the postmaster but none of the children. And it will
be very fragile, as only root can do it.

>
> And maybe add a note to the docs telling people to disable memory
> overcommit on dedicated database servers if that isn't already there...
>
>

It is there, and has been for years.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-02-02 20:17:29 Re: configurability of OOM killer
Previous Message David Fetter 2008-02-02 19:43:32 Re: Truncate Triggers