> > I use mod_gzip (http://www.remotecommunications.com/apache/mod_gzip/)
with
> > the following configuration:
>
> Thanks, it works and it's cool.
>
:-)
> I just wanted to add that my production server does a funny thing: when
> I enable mod_gzip for Embperl pages Apache somehow manages to leave idle
> Postgres child after each request and it breaks down soon on 'too many
> postgres clients'. Maybe it has something to do with my custom auth
> modul that connects and then pass around db handle in pnotes (this I
> forget to disconnect, of course, but it used to work), I'll look at it
> closer soon. My test server (identical configuration, RH62, latest RPMs)
> works fine.
>
pnotes is destroyed at the end of the request, so your database handle
should be closed automaticly.
mod_gzip changes the way your request is called. mod_gzip takes the request,
changes some internal Apache pointers, so it get the output of the content
handler (which isn't possible with the standart Apache API in 1.3) and then
calls your content handler as a sub request. I don't know how mod_perl
handles pnotes in subrequests. Maybe there is a bug in mod_perl, that
prevents pnotes from being correctly destroyed in this case. I think the
best would be to regsister a cleanup handler, that makes sure the database
handle is closed at the end of the request.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
