Re: mod_auth_pgsql 2.0.1 don't close the backend connection - Mailing list pgsql-general

From Richard Huxton
Subject Re: mod_auth_pgsql 2.0.1 don't close the backend connection
Date
Msg-id 200310011540.40127.dev@archonet.com
Whole thread Raw
In response to Re: mod_auth_pgsql 2.0.1 don't close the backend connection  (Vivek Khera <khera@kcilink.com>)
List pgsql-general
On Wednesday 01 October 2003 15:17, Vivek Khera wrote:
> >>>>> "KJ" == Kris Jurka <books@ejurka.com> writes:
> >>
> >> Is it a bug in the mod_auth_pgsql that don't close the connection or is
> >> it a setup somewhere ?
>
> KJ> Yes, the mod_auth_pgsql series for Apache 2 is broken as you describe.
> It KJ> does not release the connection, but the change is intentional.
> Looking KJ> at the Changelog I see:
>
> Is not that the whole point of a child exit handler in apache?  when
> each child exits, it calls a handler in each module that registers one
> so that it can do whatever cleanup it needs, such as closing the
> database handle.  This facility was even available in apache 1.x.

I think the problem is that Apache is pre-forking a batch of child processes
that sit there using up all his connections.

--
  Richard Huxton
  Archonet Ltd

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql error: cannot open libpq.so.3
Next
From: Tom Lane
Date:
Subject: Re: Is the use of array as PL/PGSQL function arguments ?