From: | Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | John Hansen <john(at)geeknet(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PG Killed by OOM Condition |
Date: | 2005-10-03 20:25:00 |
Message-ID: | 4341939C.6060505@empires.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
> On Mon, Oct 03, 2005 at 11:03:06PM +1000, John Hansen wrote:
>
>>Might it be worth while protecting the postmaster from an OOM Kill on
>>Linux by setting /proc/{pid}/oom_adj to -17 ?
>>(Described vaguely in mm/oom_kill.c)
>
>
> Has it actually happened to you? PostgreSQL is pretty good about its
> memory usage. Besides, seems to me it should be an system admisitrator
> descision.
>
It's happened to me...
Usually it's when there's some other runaway process, and the kernel
decides to kill PostgreSQL because it can't tell the difference.
I really don't like that "feature" in linux. Nobody has been able to
explain to me why linux is the only OS with an OOM Killer. If someone
here has more information, I'd like to know.
When using linux I always set vm_overcommit=2.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-10-03 20:28:41 | Re: [HACKERS] External Sort timing debug statements |
Previous Message | Alvaro Herrera | 2005-10-03 20:12:25 | Re: Vacuum Full Analyze Stalled |