Luiz Bernardi wrote:
I am developing a system, using the ZeosLib, which maintains a
permanent connection to the database.
When the client loses the connection, the server does not recognize
this and keeps the connection as if it were active. When the client
attempts to reconnect, the server creates a new connection and the
previous remains active.
how does this happen ? TCP connections don't just wander off and get lost.
This has caused an excessive increase in the number of active
connections and hampered the use of the system.
Have any way or setting to make postgres close idle connections?
first, you'd have to identify that they were in fact 'lost' and not just
idle. we have apps that open a socket to postgres, issue some
commands, then sometimes sit for hours before more commands are issued.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
