On Wed, 2003-01-29 at 21:52, Marc G. Fournier wrote:
> The problem is/was persistent database connections ... the problem, IMHO,
> is that there is no way of 'timing out' idle connections, so any load on
> the web site that creates a whack of persistent connections, and then they
> all go idle, then if another hit on a different database goes through, it
> gets starved for connections ...
Couldn't that easily be handled by the client interface (PHP, in this
case) that provides support for persistent connections?
(Assuming that you're suggesting that we add support for timing out
sessions to the backend -- if you're not, my apologies.)
Cheers,
Neil
--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC