| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tory M Blue <tmblue(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: oom_killer |
| Date: | 2011-04-21 13:02:44 |
| Message-ID: | BANLkTi=X-bHbhP0O=eS-Pc5N3omRHtD=Fg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Apr 21, 2011 at 2:53 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
> On Thu, Apr 21, 2011 at 2:48 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>
>> There's probably something else that's trying to grab all the memory and
>> then tries to use it and PG ends up getting nailed because the kernel
>> over-attributes memory to it. You should be looking for that other
>> process..
>
> Not only that, you probably should set up your oom killer not to kill
> postmaster. Ever.
>
Here: http://developer.postgresql.org/pgdocs/postgres/kernel-resources.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-04-21 14:27:40 | Re: oom_killer |
| Previous Message | Claudio Freire | 2011-04-21 12:53:35 | Re: oom_killer |