| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changing the default configuration (was Re: [pgsql-advocacy] |
| Date: | 2003-02-11 18:34:32 |
| Message-ID: | Pine.LNX.4.33.0302111132030.29884-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers pgsql-performance |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2003-02-11 18:53:51 | Re: Changing the default configuration (was Re: [pgsql-advocacy] |
| Previous Message | mlw | 2003-02-11 18:27:19 | Re: [HACKERS] Changing the default configuration (was Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mlw | 2003-02-11 18:44:15 | location of the configuration files |
| Previous Message | mlw | 2003-02-11 18:27:19 | Re: [HACKERS] Changing the default configuration (was Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2003-02-11 18:53:51 | Re: Changing the default configuration (was Re: [pgsql-advocacy] |
| Previous Message | mlw | 2003-02-11 18:27:19 | Re: [HACKERS] Changing the default configuration (was Re: |