On Mon, 02 May 2005 13:59:21 +0300 Hannu Krosing <[EMAIL PROTECTED]> wrote: >On E, 2005-05-02 at 01:35 -0400, Tom Lane wrote:
>Well, I've had problems with clients which resolve DB timeouts by >closing the current connection and establish a new one. > >If it is actual DB timeout, then it all is ok, the server >soon notices that the client connection is closed and kills itself. > >Problems happen when the timeout is caused by actual >network problems - when i have 300 clients (server's max_connections=500) >which try to reconnect after network outage, only 200 of them can do so >as the server is holding to 300 old connections. > >In my case this has nothing to do with locks or transactions. Yes, but if you would have locks then same problem occours.. >It would be nice if I coud st up some timeut using keepalives (like ssh-s ProtocoKeepalives") and >use similar timeouts on client and server. Diffrent ppl use diffrent OS. Adnan DURSUN ASRIN Bilişim Hiz.Ltd. ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
