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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: kuznet(at)ms2(dot)inr(dot)ac(dot)ru
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 19:52:30
Message-ID: 28329.962740350@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
kuznet(at)ms2(dot)inr(dot)ac(dot)ru writes:
>> 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.

As I recall, the original complaint was precisely that Linux discards
the server->client data instead of allowing the client to read it.  This
was on a single machine, so there's no issue of whether it got lost in
the network.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-07-04 19:56:31
Subject: Re: Changes to handling version numbers internally
Previous:From: Egon SchmidDate: 2000-07-04 19:51:11
Subject: Re: Article on MySQL vs. Postgres

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