Re: configurability of OOM killer

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