Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id CCC11DA629A for ; Wed, 1 Aug 2012 14:49:07 -0300 (ADT) Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Swd2e-0000QZ-Hy for pgsql-admin@postgresql.org; Wed, 01 Aug 2012 17:49:06 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Wed, 01 Aug 2012 12:48:50 -0500 Message-Id: <501925AD020000250004932E@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.2 Date: Wed, 01 Aug 2012 12:48:45 -0500 From: "Kevin Grittner" To: "pgsql-admin" , "Radovan Jablonovsky" Subject: Re: PostgreSQL oom_adj postmaster process to -17 References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201208/2 X-Sequence-Number: 39823 Radovan Jablonovsky wrote: > We are running PostgreSQL version 9.1.1 You should apply the latest bug fixes by updating to 9.1.4. http://www.postgresql.org/support/versioning/ > with 32GB of RAM, 32GB of SWAP and during high load we could reach > (swap + RAM) memory limit. If you're even *starting* to swap you're doing something wrong, much less exhausting swap space equal to actual RAM. What is your configuration? http://wiki.postgresql.org/wiki/Server_Configuration While it's probably a good idea to configure the OOM killer to behave more sanely, we tend to ignore it in favor of ensuring that it never comes into play. We run about 200 databases 24/7 and I think I've seen it kick in about twice -- when we ran queries that leaked memory on each row in a big query. -Kevin