Horton

Re: Windows: Wrong error message at connection termination

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Lars Kanis <lars@greiz-reinsdorf.de>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-11-21T21:42:46Z
Lists: pgsql-hackers 
Thomas Munro <thomas.munro@gmail.com> writes:
> Hmm, maybe it's still not enough.  Now that I have coffee, I thought
> about the well known failure of idle_in_transaction_timeout to report
> errors on Windows[1].

Yeah, I think that may well be a manifestation of the same problem:
once the backend exits, Winsock issues RST which prevents the client
from reading the queued data.  We had been analyzing that under the
assumption that Windows obeys the TCP RFCs ... but having now been
disabused of that optimism, it seems to match up pretty well.
It'd be useful to check if Lars' patch cures that symptom.

			regards, tom lane

Commits

  1. On Windows, close the client socket explicitly during backend shutdown.