Re: PostgreSQL oom_adj postmaster process to -17

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>
*