On Wednesday 30 October 2002 20:09, Tom Lane wrote:
> This strikes me as a fault on the client side, not in Postgres --- to
> wit, poor connection management. It is not Postgres' job to kill idle
> client connections.
I suppose you are right. The thing is we have never used persistant
connection
Denis Braekhus <[EMAIL PROTECTED]> writes:
> Every now and then postgresql gets "too busy" and these patterns emerge :
> - some connections are just idling and not being reaped (presumably either the
> browser/client or the apache webserver timed out the request)
> - these connections stack up to
Hi all,
Anyone experienced similar patterns on their Web-DB setups ?
Short setup description :
X frontend webservers (Apache 1.3.x) with php and mod_perl dynamic content.
1 backend db server (Postgresql 7.1.3).
The webservers are _very_ busy, but send only a limited amount of their
requests t
