From: | <adnandursun(at)asrinbilisim(dot)com(dot)tr> |
---|---|
To: | Alvar Freude <alvar(at)a-blast(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Feature freeze date for 8.1 |
Date: | 2005-05-02 13:24:57 |
Message-ID: | web-96115722@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:32:18 +0200
Alvar Freude <alvar(at)a-blast(dot)org> wrote:
>Hi,
>
>-- Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> wrote:
>
>> The tcp hackers have provided an api for clients to set
>these values per
>> socket (setsockopt with TCP_KEEPIDLE and similar (in
>linux at least)).
>
>you can use SO_KEEPALIVE:
>
> [...] SO_KEEPALIVE enables
> the periodic transmission of messages on a connected
socket. Should the
> connected party fail to respond to these messages, the
connection is con-
> sidered broken and processes using the socket are
notified via a SIGPIPE
> signal when attempting to send data.
>
>
>For me it seems to be a good idea to support this. For the
applications
>(server, client) it is transparent, but notices a cutted
or broken network
>connection faster then before...
>
>But even with this you only realise that the connection is
>gone when sending something, AFAIK.
So this means, If client does never try to send data the
resources would be going to be held.
I think it is not a good solution to find zombie / dead
connection and clear them..
Best Regards,
Adnan DURSUN
ASRIN Bilişim Hiz.Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-02 14:33:59 | Re: Feature freeze date for 8.1 |
Previous Message | Hannu Krosing | 2005-05-02 11:54:35 | Re: How to make lazy VACUUM of one table run in several |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-02 14:33:59 | Re: Feature freeze date for 8.1 |
Previous Message | Alvar Freude | 2005-05-02 11:32:18 | Re: Feature freeze date for 8.1 |