From: | Rajesh Kumar Mallah <mallah(at)trade-india(dot)com> |
---|---|
To: | James Taylor <jtx(at)hatesville(dot)com> |
Cc: | "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Idle processes won't die |
Date: | 2004-02-25 01:30:14 |
Message-ID: | 403BFAA6.8090906@trade-india.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Dear James,
We have been using mod_perl with PostgreSQL in web environment
without any problems. I hope you are already using Apache::DBI for
connection pooling.
Regds
Mallah
James Taylor wrote:
> Hi everyone, using mod_perl with Postgres, postgres is on the same
> server as the webserver. Perl is opening connections, and then
> closing them at the end of every script, however Pg
> is refusing to close the connection, and I have tons and tons of Idle
> processes sitting around, which causes the web site to crash because
> the maximum number of pgsql processes gets reached after the site is
> accessed 32 times. From everything I know about Perl, even if I
> didn't implicitly close the database handles, the perl garbage handler
> would close them for me. Is there some sort of configuration for
> postgres to disallow all these idle processes from sticking around, so
> they maybe... close themselves after 5 seconds or something similar?
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Holzheu | 2004-02-25 07:58:03 | Re: Problems with pg_dump |
Previous Message | Tom Lane | 2004-02-24 23:56:55 | Re: Idle processes won't die |