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

From Tom Lane
Subject Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection
Date
Msg-id 28329.962740350@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection  (kuznet@ms2.inr.ac.ru)
Responses Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection  (kuznet@ms2.inr.ac.ru)
List pgsql-hackers
kuznet@ms2.inr.ac.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)
Next
From: "Mikheev, Vadim"
Date:
Subject: RE: Article on MySQL vs. Postgres