From: | <adnandursun(at)asrinbilisim(dot)com(dot)tr> |
---|---|
To: | Hannu Krosing <hannu(at)skype(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, Oliver Jowett <oliver(at)opencloud(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Feature freeze date for 8.1 |
Date: | 2005-05-02 11:23:01 |
Message-ID: | web-96062019@mail3.doruk.net.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, 02 May 2005 13:59:21 +0300
Hannu Krosing <hannu(at)skype(dot)net> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | adnandursun | 2005-05-02 11:25:26 | Re: Feature freeze date for 8.1 |
Previous Message | Hannu Krosing | 2005-05-02 10:59:21 | Re: Feature freeze date for 8.1 |
From | Date | Subject | |
---|---|---|---|
Next Message | adnandursun | 2005-05-02 11:25:26 | Re: Feature freeze date for 8.1 |
Previous Message | Hannu Krosing | 2005-05-02 10:59:21 | Re: Feature freeze date for 8.1 |