| From: | "Brett W(dot) McCoy" <bmccoy(at)chapelperilous(dot)net> |
|---|---|
| To: | "D(dot) Duccini" <duccini(at)backpack(dot)com> |
| Cc: | Pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Release connections in MODPERL |
| Date: | 2001-01-11 02:50:30 |
| Message-ID: | Pine.LNX.4.30.0101102028180.19850-100000@chapelperilous.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Wed, 10 Jan 2001, D. Duccini wrote:
> normally in PERL it shuts it down when the perl goes away, but in mod
> perl, it doesn't go away
Yes, mod_perl keeps your code in memory, and you can't be sloppy like you
can be with plain old CGI, so you need to explicitly close your database
conenctions (in DBI, I think it's the disconnect() method).
Note also, if you are using Apache::DBI, it does some cool things like
connection pooling and stuff, specifically for use with mod_perl.
-- Brett
http://www.chapelperilous.net/~bmccoy/
---------------------------------------------------------------------------
I know how to do SPECIAL EFFECTS!!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2001-01-11 02:57:56 | Re: Release connections in MODPERL |
| Previous Message | D. Duccini | 2001-01-11 00:05:35 | Release connections in MODPERL |