Re: mod_auth_pgsql 2.0.1 don't close the backend connection

From: Richard Huxton <dev(at)archonet(dot)com>
To: Vivek Khera <khera(at)kcilink(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: mod_auth_pgsql 2.0.1 don't close the backend connection
Date: 2003-10-01 14:40:40
Message-ID: 200310011540.40127.dev@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday 01 October 2003 15:17, Vivek Khera wrote:
> >>>>> "KJ" == Kris Jurka <books(at)ejurka(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-10-01 14:52:47 Re: Is the use of array as PL/PGSQL function arguments ?
Previous Message Tom Lane 2003-10-01 14:34:54 Re: psql error: cannot open libpq.so.3