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

Re: PostgreSQL oom_adj postmaster process to -17

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Radovan Jablonovsky <radovan(dot)jablonovsky(at)replicon(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: PostgreSQL oom_adj postmaster process to -17
Date: 2012-08-09 01:33:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On 08/09/2012 04:24 AM, Kevin Grittner wrote:
Can we please please PLEASE link to that as a comment above max_connections?

Last time this came up nobody was happy with wording of a comment so 
nothing got done. It's a real usability wart - causing real-world 
performance and reliability problems - that people unwittingly raise 
max_connections to absurd levels because they get no warnings, hints or 
guidance of any sort.

Craig Ringer

In response to


pgsql-admin by date

Next:From: Sergey KonoplevDate: 2012-08-09 10:25:06
Subject: Re: Streaming replication failover with 3 servers
Previous:From: Kevin GrittnerDate: 2012-08-08 20:24:08
Subject: Re: PostgreSQL oom_adj postmaster process to -17

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