From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Aras Angelo <araskoktas(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: idle connections |
Date: | 2009-10-06 00:51:22 |
Message-ID: | dcc563d10910051751l3603440xd040b73f3b89f88a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Oct 5, 2009 at 5:50 PM, Aras Angelo <araskoktas(at)gmail(dot)com> wrote:
> Its a regular pg_connect()
>
> When i kill the earliest idle process the others stop too. So i dont know
> whats wrong really. All our apps use the same footer, with pg_close() at the
> end.
>
> I have done most of the things you guys suggested, so it seems to me that
> something between php-apache-postgresql is not doing good, and it only
> effects us at peak times, so just wondering if killing processes every 2-3
> minutes, would do harm on our setup.
>
> I have 3 apache servers reading from one single db server.
So what's your max apache children / threads and what's your max pgsql
connections allowed? You may need to crank up pgsql connection limit
to keep up.
From | Date | Subject | |
---|---|---|---|
Next Message | Olivier Nicole | 2009-10-06 04:19:45 | postgres 8.4 authentication with LDAP |
Previous Message | Scott Marlowe | 2009-10-06 00:50:02 | Re: idle connections |