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: Fri, 25 Feb 2022 07:02:13 -0600
Message-ID: <20220225130213.GB9008@telsasoft.com> (raw)
In-Reply-To: <20220224020005.GT9008@telsasoft.com>
On Wed, Feb 23, 2022 at 07:04:15PM -0600, Justin Pryzby wrote:
> And the aforementioned network trace. You could set a capture filter on TCP
> SYN|RST so it's not absurdly large. From my notes, it might look like this:
> (tcp[tcpflags]&(tcp-rst|tcp-syn|tcp-fin)!=0)
I'd also add '|| icmp'. My hunch is that you'll see some ICMP (not "ping")
being sent by an intermediate gateway, resulting in the connection being reset.
--
Justin
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: <20220225130213.GB9008@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