Bruce>Well, we could have the connection pooler disconnect those, right?
I agree. Do you think we could rely on all the applications being configured in a sane way?
A fallback configuration at DB level could still be useful to ensure the DB keeps running in case multiple applications access it. It might be non-trivial to ensure proper configurations across all the apps.
What I do like is the behaviour of dropping connections should already be considered by existing applications, so it should fit naturally to the existing apps.
Alternative approach might be to dump to disk relevant resources for inactive sessions, so the session could be recreated in case the connection is requested again after a long pause (e.g. reprepare all the statements), however it sounds scary.
Vladimir
