Re: An I/O error occurred while sending to the backend (PG 13.4) - Mailing list pgsql-performance

From Justin Pryzby
Subject Re: An I/O error occurred while sending to the backend (PG 13.4)
Date
Msg-id 20220225130213.GB9008@telsasoft.com
Whole thread Raw
In response to Re: An I/O error occurred while sending to the backend (PG 13.4)  (Justin Pryzby <pryzby@telsasoft.com>)
Responses RE: An I/O error occurred while sending to the backend (PG 13.4)  ("ldh@laurent-hasson.com" <ldh@laurent-hasson.com>)
List 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



pgsql-performance by date:

Previous
From: "Kumar, Mukesh"
Date:
Subject: RE: Slow Running Queries in Azure PostgreSQL
Next
From: Ayub Khan
Date:
Subject: slow query to improve performace