Attached is a new patch that I think addresses your concerns. ________________________________ From: Tom Lane <t...@sss.pgh.pa.us> Sent: Thursday, September 30, 2021 16:04 To: Jelte Fennema <jelte.fenn...@microsoft.com> Cc: pgsql-hack...@postgresql.org <pgsql-hack...@postgresql.org> Subject: [EXTERNAL] Re: Add ETIMEDOUT to ALL_CONNECTION_FAILURE_ERRNOS
Jelte Fennema <jelte.fenn...@microsoft.com> writes:
> Previously successfully opened TCP connections can still fail on reads
> with ETIMEDOUT. This should be considered a connection failure, so that
> the connection in libpq is marked as CONNECTION_BAD. The reason I got an
> ETIMEDOUT was, because I had set a low tcp_user_timeout in the
> connection string. However, it can probably also happen due to
> keepalive limits being reached.
I'm dubious about the portability of this patch, because we don't
use ETIMEDOUT elsewhere. strerror.c thinks it may not exist,
which is probably overly conservative because POSIX has required
it since SUSv2. The bigger problem is that it's not accounted for in
the WSAxxx mapping done in port/win32_port.h and TranslateSocketError.
That'd have to be fixed for this to behave reasonably on Windows,
I think.
regards, tom lane
0001-Consider-ETIMEDOUT-a-connection-failure.patch
Description: 0001-Consider-ETIMEDOUT-a-connection-failure.patch
