From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Andrej <andrej(dot)groups(at)gmail(dot)com> |
Cc: | Yang Zhang <yanghatespam(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Preventing OOM kills |
Date: | 2011-05-25 00:53:33 |
Message-ID: | BANLkTikGEq2Gji8UQXS4p-F9eb_EoucCXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 24, 2011 at 6:50 PM, Andrej <andrej(dot)groups(at)gmail(dot)com> wrote:
> On 25 May 2011 12:32, Yang Zhang <yanghatespam(at)gmail(dot)com> wrote:
>> PG tends to be picked on by the Linux OOM killer, so lately we've been
>> forcing the OOM killer to kill other processes first with this script:
>>
>> while true; do
>> for i in `pgrep postgres`; do
>> echo -17 > /proc/$i/oom_adj
>> done
>> sleep 60
>> done
>>
>> Is there a Better Way? Thanks in advance.
>
> Add more RAM? Look at tunables for other processes on
> the machine? At the end of the day making the kernel shoot
> anything out of despair shouldn't be the done thing.
I thought that setting vm.overcommit_memory=2 stopped the OOM killer.
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2011-05-25 00:57:30 | Re: Preventing OOM kills |
Previous Message | Andrej | 2011-05-25 00:50:09 | Re: Preventing OOM kills |