> -----Original Message----- > From: Justin Pryzby <pryzby@xxxxxxxxxxxxx> > Sent: Friday, February 25, 2022 08:02 > To: ldh@xxxxxxxxxxxxxxxxxx > Cc: pgsql-performance@xxxxxxxxxxxxxx > Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > > 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 Hello Justin, I am so sorry but I do not understand what you are asking me to do. I am unfamiliar with these commands. Is this a postgres configuration file? Is this something I just do once or something I leave on to hopefully catch it when the issue occurs? Is this something to do on the DB machine or the ETL machine? FYI: - My ETL machine is on 10.64.17.211 - My DB machine is on 10.64.17.210 - Both on Windows Server 2012 R2, x64 So sorry for the bother, Laurent.
