Hi everyone,
Well, here's an update. VERY preliminary tests show that the PostgreSQL
message in question is not caused by the child exiting. I have a 1
MacClients prefork Apache with MaxRequestsPerChild of 5 and I have a
'warn' statement on the PerlChildExitHandler to alert me when the child
exits
Stas Bekman wrote:
Also it's possible that using Apache::DBI is the better solution, but it
depends on your demands.
doh! please ignore me, instead listen to Perrin. Obviously I've missed the
big letters saying that you already use Apache::DBI.
--
On Tue, 2004-12-21 at 09:26 -0500, Joel wrote:
> And from what I understand, this is caused when the Apache child exists
> and does not execute an explicit $dbh->disconnect() on the database
> handle. That is, the connection is not being closed properly before the
> handle goes out of scope.
That'
Joel wrote:
Good morning,
This is not a problem, per se, nor is it something I especially need to
get done, but it would certainly be nice to have and might, in some small
way, benefit the world in general. Here's what's going on:
I am using mod_perl 1.99_13 (yes, I know I should upgrade) and Apach
