Date: Thu, 21 Apr 2011 08:48:51 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Tory M Blue <tmblue@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: oom_killer
Message-ID: <20110421124851.GC4548@tamriel.snowman.net>
References: <BANLkTinXiV8ODPP5SwOOwdR5Nstdk98pcw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="TCH5zSpbvKOKdCih"
Content-Disposition: inline
In-Reply-To: <BANLkTinXiV8ODPP5SwOOwdR5Nstdk98pcw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)


--TCH5zSpbvKOKdCih
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Tory M Blue (tmblue@gmail.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
run.

> 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
process..

	Thanks,

		Stephen

--TCH5zSpbvKOKdCih
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk2wJ7MACgkQrzgMPqB3kihHiACeLJNPMIKhVw+8R5Au1cuFq/yA
ztYAnRI7CszMBeHEBTtsrtyu6KBszvLf
=TCL+
-----END PGP SIGNATURE-----

--TCH5zSpbvKOKdCih--