By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,852 Members | 2,198 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,852 IT Pros & Developers. It's quick & easy.

Idle connections - Too many clients connected already

P: n/a

After using Postgresql for a while, through ODBC / MS Access, I'm not
able to connect to the server anymore. The server reports "Too many
clients connected already".

With a "ps -afx", I can see a lot of idle postgresql connections, which
correspond for sure to ODBC connections that haven't been closed
properly, and that remain opened. Stopping and restarting the server
solves the problem.

Is there a way to avoid that? I cannot certifiy that clients will always
close their connexions in a clean way. So, is the server able to check
if clients are still alive, and close their connexion if it's not the
case? I never had anything like that with MS SQL Server...



---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******

Nov 22 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.