Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL oom_adj postmaster process to -17

From: Radovan Jablonovsky <radovan(dot)jablonovsky(at)replicon(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: PostgreSQL oom_adj postmaster process to -17
Date: 2012-08-08 20:04:10
Message-ID: CAJYcdTsgGYacbAs1St3CuSJRHr7ANHDH4t04CxCiEXfqbX+ekg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
Currently there are maximum 600 connections.

On Fri, Aug 3, 2012 at 2:05 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:

> On Fri, Aug 3, 2012 at 12:08 PM, Radovan Jablonovsky
> <radovan(dot)jablonovsky(at)replicon(dot)com> wrote:
> > Thanks you for your response.
> >
> > Database config:
> > shared_buffers = 8GB
> > temp_buffers = 32MB
> > work_mem = 64MB
> > maintenance_work_mem = 512MB
> > effective_cache_size = 16GB
> >
> > In usual load there are not much pressure on memory, but it is possible
> to
> > have all clients start using heavy reports. They are valid requests and
> > could consume all memory. In this border and not likely but possible
> > scenario it could be useful to let OOM killer to kill client's
> > processes/connections but leave PostgreSQL system processes (postmaster,
> > writer, stat, log, streaming, ...) excluded  from reach of OOM killer.
>
> You're only realistic solution is to either limit the incoming
> connections via a connection pooler like pgbouncer or to lower your
> work_mem to something smaller. What's you're current max connections
> setting?
>



-- 

*Radovan Jablonovsky* | SaaS DBA | Phone 1-403-262-6519 (ext. 256) | Fax
1-403-233-8046****


*

Replicon | Hassle-Free Time & Expense Management Software - 7,300 Customers
- 70 Countries
www.replicon.com | facebook <http://www.facebook.com/Replicon.inc> |
twitter<http://twitter.com/Replicon>
 | blog <http://www.replicon.com/blog/> | contact
us<http://www.replicon.com/about_replicon/contact_us.aspx>

We are hiring! | search
jobs<http://tbe.taleo.net/NA2/ats/careers/searchResults.jsp?org=REPLICON&cws=1&act=sort&sortColumn=1&__utma=1.651918544.1299001662.1299170819.1299174966.10&__utmb=1.8.10.1299174966&__utmc=1&__utmx=-&__utmz=1.1299174985.10.3.utmcsr=google%7Cutmccn=(organic)%7Cutmcmd=organic%7Cutmctr=replicon%20careers&__utmv=1.%7C3=Visitor%20Type=Prospects=1,&__utmk=40578466>
*

In response to

Responses

pgsql-admin by date

Next:From: Kevin GrittnerDate: 2012-08-08 20:24:08
Subject: Re: PostgreSQL oom_adj postmaster process to -17
Previous:From: Amador AlvarezDate: 2012-08-08 17:34:54
Subject: Re: standby with a fixed lag behind the master

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group