Re: An I/O error occurred while sending to the backend (PG 13.4)

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: ldh(at)laurent-hasson(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: An I/O error occurred while sending to the backend (PG 13.4)
Date: 2022-02-25 13:02:13
Message-ID: 20220225130213.GB9008@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ayub Khan 2022-02-25 20:18:22 slow query to improve performace
Previous Message Kumar, Mukesh 2022-02-25 12:41:33 RE: Slow Running Queries in Azure PostgreSQL