pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: ldh@laurent-hasson.com
Cc: pgsql-performance@postgresql.org
Subject: Re: An I/O error occurred while sending to the backend (PG 13.4)
Date: Wed, 23 Feb 2022 20:00:05 -0600
Message-ID: <20220224020005.GT9008@telsasoft.com> (raw)
In-Reply-To: <MN2PR15MB256034941F279136BA555236853D9@MN2PR15MB2560.namprd15.prod.outlook.com>
References: <MN2PR15MB2560DC71C217FF03AC9082F5856B9@MN2PR15MB2560.namprd15.prod.outlook.com>
	<20211204175926.GC17618@telsasoft.com>
	<MN2PR15MB256038B438B8990D08B4A991856B9@MN2PR15MB2560.namprd15.prod.outlook.com>
	<MN2PR15MB256034941F279136BA555236853D9@MN2PR15MB2560.namprd15.prod.outlook.com>

You originally mailed about an error on the client, and now you found
corresponding server logs, which suggests a veritable network issue.

Are the postgres clients and server on the same subnet ?  If not, what are the
intermediate routers ?  Is there any NAT happening ?  Do those devices have any
interesting logs that correspond with the server/client connection failures ?

Have you tried enabling TCP keepalives ?  This might help to convince a NAT
device not to forget about your connection.

https://www.postgresql.org/docs/current/runtime-config-connection.html
tcp_keepalives_idle=9
tcp_keepalives_interval=9
tcp_keepalives_count=0
tcp_user_timeout=0 -- You apparently have this set, but it cannot work on windows, so just generates noise.

On linux, you can check the keepalive counters in "netstat -not" to be sure
that it's enabled.  A similar switch hopefully exists for windows.

-- 
Justin





view thread (25+ messages)  latest in thread

Message-ID: <20220224020005.GT9008@telsasoft.com>
Permalink:  ../20220224020005.GT9008@telsasoft.com/
Also on:    postgresql.org/message-id/20220224020005.GT9008@telsasoft.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pryzby@telsasoft.com, ldh@laurent-hasson.com
  Subject: Re: An I/O error occurred while sending to the backend (PG 13.4)
  In-Reply-To: <20220224020005.GT9008@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox