Postgres Pro
Downloads
Home   >   mailing lists

Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection - Mailing list pgsql-hackers

From Alan Cox
Subject Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection
Date
Msg-id E139GDn-0005te-00@the-village.bc.nu
Whole thread Raw
In response to Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
> No, it doesn't "hang for all eternity", it sits in the same state until
> (a) the client side closes its sending side of the connection (ie, sends
> FIN), or (b) the FIN-WAIT-1 state times out.  But given a normally
> responsive client and no loss of physical connectivity or crash of
> either TCP stack, there is no connection reset and no failure to deliver
> sent data.

I cannot ack the data since it has not been read, so how can I ack the fin ?

pgsql-hackers by date:

Previous
From: Alan Cox
Date:
Subject: Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection
Next
From: JanWieck@t-online.de (Jan Wieck)
Date:
Subject: Re: Article on MySQL vs. Postgres