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

From kuznet@ms2.inr.ac.ru
Subject Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection
Date
Msg-id 200007041757.VAA25791@ms2.inr.ac.ru
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>)
Responses 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
Hello!

> blunt instrument for reporting it, because it causes loss of data going
> in the other direction.

First. Data, which reached the host are not lost.

Second. TCP may lose this data because this data did not reach host
before reset arrived, indeed.

After the second we arrive at the next: if you send to dead pipe,
or do not read some remnant of data before closing, it is _HARD_ bug
in your application or in protocol.

Do you understand what hard bug is? It is when further behaviour
is unpredictable and the state cannot be recovered. Essentially,
it is thing which exceptions and fatal signals are invented for. 8)

Alexey


pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: vacation
Next
From: The Hermit Hacker
Date:
Subject: Re: [GENERAL] Revised Copyright: is this more palatable?