Re: PostgreSQL oom_adj postmaster process to -17

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "pgsql-admin" <pgsql-admin(at)postgresql(dot)org>, "Radovan Jablonovsky" <radovan(dot)jablonovsky(at)replicon(dot)com>
Subject: Re: PostgreSQL oom_adj postmaster process to -17
Date: 2012-08-01 17:48:45
Message-ID: 501925AD020000250004932E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Radovan Jablonovsky <radovan(dot)jablonovsky(at)replicon(dot)com> 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ascarabina 2012-08-01 19:05:30 Re: Could You help me
Previous Message Gary Webster 2012-08-01 15:43:24 [pgsql] How bad is this full vacuum error?