At 10:52 PM 1/29/03 -0400, 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 ...
Why does it get starved for connections if there are idle ones? Why can't
the idle ones connect to a different DB?
Also since the pages showed most of the usual info along with the error
messages, I'd assume that being unable to connect to those databases isn't
such a serious problem, in which case the webapp shouldn't have to display
such ugliness to the user and just show as much of the usual info as
possible and send the errors out of band - to the system logs or such.
In some cases one could make sure the dynamic content webserver's max
connection setting is < Postgresql's max backends. The static content
webserver(s) could have a much higher max connection setting.
Regards,
Link.
