Re: oom_killer

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tory M Blue <tmblue(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: oom_killer
Date: 2011-04-21 12:48:51
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-performance

* Tory M Blue (tmblue(at)gmail(dot)com) wrote:
> Is there anyone that could help me understand why all of a sudden with
> no noticeable change in data, no change in hardware, no change in OS,
> I'm seeing postmaster getting killed by oom_killer?

You would really be best off just turning off the oom_killer.. Of
course, you should probably also figure out what process is actually
chewing through your memory to the point that the OOM killer is getting

> The dmesg shows that swap has not been touched free and total are the
> same, so this system is not running out of total memory per say.

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



In response to

  • oom_killer at 2011-04-21 08:28:45 from Tory M Blue


Browse pgsql-performance by date

  From Date Subject
Next Message Claudio Freire 2011-04-21 12:53:35 Re: oom_killer
Previous Message yoshi watanabe 2011-04-21 12:37:11 Re: oom_killer