Skip site navigation (1) Skip section navigation (2)

Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection

From: kuznet(at)ms2(dot)inr(dot)ac(dot)ru
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: alan(at)lxorguk(dot)ukuu(dot)org(dot)uk, dyp(at)perchine(dot)com, pgsql-hackers(at)postgresql(dot)org, davem(at)redhat(dot)com
Subject: Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection
Date: 2000-07-04 17:57:28
Message-ID: 200007041757.VAA25791@ms2.inr.ac.ru (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew SullivanDate: 2000-07-04 18:13:59
Subject: Re: Revised Copyright: is this more palatable?
Previous:From: Michael MeskesDate: 2000-07-04 17:56:26
Subject: vacation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group