From: | "Richard Huxton" <dev(at)archonet(dot)com> |
---|---|
To: | "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: hung back end |
Date: | 2001-02-09 10:23:32 |
Message-ID: | 004101c09294$fb715ea0$1001a8c0@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- Original Message -----
From: "Thomas T. Thai" <tom(at)minnesota(dot)com>
> i'm porting some apps from mysql to pgsql and i'm using php4.0.5-cvs with
> phplib db classes. i'm starting to see that when ever i load a web page,
> it starts a backend. then when i try to reload the page, i get:
>
> sure i could increase the # of child processes, but instead i decided to
> check why it was doing this. it appears that after a webpage is openned, a
> new child process or backend starts. the persistent link doesn't seem to
> exist any longer. on the next reload, a new process. but the old one never
> disappeared. it'll sit there for hours and days.
IIRC there is a known problem with PHP's cached db connections to postgres.
Basically, as you've seen it doesn't reuse old backends, so you run out of
connections. See the archive for details. I think someone is looking at this
on the PHP side.
- Richard Huxton
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph | 2001-02-09 11:17:21 | Checking Permissions with SQL |
Previous Message | Ben Leslie | 2001-02-09 09:00:10 | Re: Database and table name case sensitivity |