Re: Changing the default configuration (was Re: [pgsql-advocacy] - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: Changing the default configuration (was Re: [pgsql-advocacy]
Date
Msg-id Pine.LNX.4.33.0302111132030.29884-100000@css120.ihs.com
Whole thread Raw
In response to Re: Changing the default configuration (was Re: [pgsql-advocacy]  (mlw <pgsql@mohawksoft.com>)
Responses Re: Changing the default configuration (was Re: [pgsql-advocacy]  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Changing the default configuration  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
My other pet peeve is the default max connections setting.  This should be 
higher if possible, but of course, there's always the possibility of 
running out of file descriptors.

Apache has a default max children of 150, and if using PHP or another 
language that runs as an apache module, it is quite possible to use up all 
the pgsql backend slots before using up all the apache child slots.

Is setting the max connections to something like 200 reasonable, or likely 
to cause too many problems?



pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: location of the configuration files
Next
From: "Merlin Moncure"
Date:
Subject: Windows SHMMAX (was: Default configuration)