Re: Feature freeze date for 8.1 - Mailing list pgsql-hackers

From Alvar Freude
Subject Re: Feature freeze date for 8.1
Date
Msg-id AF5E4C8147107C3795AA3B8B@Chefkoch.local
Whole thread Raw
In response to Re: Feature freeze date for 8.1  (Dennis Bjorklund <db@zigo.dhs.org>)
Responses Re: Feature freeze date for 8.1
List pgsql-hackers
Hi,

-- Dennis Bjorklund <db@zigo.dhs.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
failto respond to these messages, the connection is con-  sidered broken and processes using the socket are notified
viaa 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.


Ciao Alvar


-- 
Alvar C.H. Freude -- http://alvar.a-blast.org/
http://odem.org/
http://www.assoziations-blaster.de/info/Hommingberger-Gepardenforelle.html
http://www.assoziations-blaster.de/

pgsql-hackers by date:

Previous
From:
Date:
Subject: Re: Feature freeze date for 8.1
Next
From: Hannu Krosing
Date:
Subject: Re: How to make lazy VACUUM of one table run in several