From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16678: The ecpg connect/test5 test sometimes fails on
 Windows
In-reply-to: <16678-253e48d34dc0c376@postgresql.org>
References: <16678-253e48d34dc0c376@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 19 Oct 2020 17:00:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <434310.1603135136.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Oct 2020 15:18:56 -0400
Message-ID: <434311.1603135136@sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> It seems that on Windows the postmaster process can close a connection
> before slow client receives a FATAL message.

Yeah, we've come to that conclusion before, see for instance

https://www.postgresql.org/message-id/flat/E1iaD8h-0004us-K9%40gemulon.pos=
tgresql.org

I haven't heard any non-unpleasant ideas for working around it.

One thought that might or might not improve matters is for
the backend to explicitly close() the socket before exiting.
We intentionally don't do that (cf 268313a95), but maybe
doing it on Windows would be better than the existing issue
--- assuming it fixes the issue, that is.

			regards, tom lane