From: yoshi watanabe <yoshi314@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: oom_killer
Date: Thu, 21 Apr 2011 14:37:11 +0200
Message-ID: <BANLkTikL1Pq5dCTWM_Qka+_ifBA-4h9bjA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinXiV8ODPP5SwOOwdR5Nstdk98pcw@mail.gmail.com>
References: <BANLkTinXiV8ODPP5SwOOwdR5Nstdk98pcw@mail.gmail.com>
Funny concidence, I was just reading up a blog post on postgres an OOM killer.
http://gentooexperimental.org/~patrick/weblog/archives/2011-04.html#e2011-04-20T21_58_37.txt
Hope this helps.
2011/4/21 Tory M Blue <tmblue@gmail.com>:
> 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?
>
> 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.
>
> I keep thinking it's something to do with lowmem vs highmem 32bit vs
> 64 bit, but again no changes and I'm getting hit nightly on 2
> different servers (running slon, so switched over and same thing, even
> disabled memory over commit and still got nailed.
>
> Is there anyone familiar with this or could take a look at the dmesg
> output (off list) and decipher it for me?
>
> this is a Fedora 12 system, 2.6.32.23-170. I've been reading and
> appears this is yet another fedora bug, but so far I have not found
> any concrete evidence on how to fix it.
>
> Fedora 12
> 32gig memory, 8 proc
> postgres 8.4.4, slony 1.20
> 5 gigs of swap (never hit it!)
>
> Thanks
> Tory
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: yoshi314@gmail.com
Subject: Re: oom_killer
In-Reply-To: <BANLkTikL1Pq5dCTWM_Qka+_ifBA-4h9bjA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox