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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

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: Sat, 24 Dec 2005 09:17:06 -0500
  • Message-id: <200512240917.06699.xzilla@users.sourceforge.net> <text/plain>

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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group