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

Re: default resource limits

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: default resource limits
Date: 2005-12-24 14:17:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
On Saturday 24 December 2005 06:22, Peter Eisentraut wrote:
> Am Samstag, 24. Dezember 2005 00:20 schrieb Andrew Dunstan:
> > The rationale is one connection per apache thread (which on Windows
> > defaults to 400). If people think this is too many I could live with
> > winding it back a bit - the defaults number of apache workers on Unix is
> > 250, IIRC.
> It's 150.  I don't mind increasing the current 100 to 150, although I find
> tying this to apache pretty bogus.
> I really don't like the prospect of making the defaults platform specific,
> especially if the only rationale for that would be "apache does it".  Why
> does apache allocate more connections on Windows anyway?

Maybe we should write something in to check if apache is installed if we're so 
concerned about that usage... I already know that I set the connection limits 
lower on most of the installations I do (given than most installations are 
not production webservers).  There is also the argument to be made that just 
because systems these days have more memory doesn't mean we have to use it. 

Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to


pgsql-hackers by date

Next:From: Simon RiggsDate: 2005-12-24 14:18:17
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous:From: Martijn van OosterhoutDate: 2005-12-24 11:50:27
Subject: Re: Fixing row comparison semantics

pgsql-patches by date

Next:From: Andrew DunstanDate: 2005-12-24 15:35:00
Subject: Re: [PATCHES] default resource limits
Previous:From: Peter EisentrautDate: 2005-12-24 11:22:31
Subject: Re: default resource limits

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