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

On Wed, Apr 13, 2022 at 03:36:19PM +, l...@laurent-hasson.com wrote: > After a lot of back and forth, someone in IT informed us that the database VM > is under a backup schedule using Veeam. Apparently, during the backup window, > Veeam creates a snapshot and that takes the VM offline for a

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

>From: Ranier Vilela ranier...@gmail.com >Sent: Thursday, March 03, 2022 13:22 > > >You are welcome. > >regards, >Ranier Vilela Hello all, After a lot of back and forth, someone in IT informed us that the database VM is under a backup schedule using Veeam.

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

Em qui., 3 de mar. de 2022 às 15:19, l...@laurent-hasson.com < l...@laurent-hasson.com> escreveu: > I am also starting to feel that the issue being on the database’s side is > less and less likely. There is something happening in between, or possibly > on the client. > > > > Ranier, the only

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

and working out with it on some plan. Thank you, Laurent. From: Ranier Vilela Sent: Thursday, March 3, 2022 11:57 To: Justin Pryzby Cc: l...@laurent-hasson.com; pgsql-performa...@postgresql.org Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) Em qui., 3 de mar. de 2022

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

Em qui., 3 de mar. de 2022 às 13:46, Justin Pryzby escreveu: > On Thu, Mar 03, 2022 at 01:33:08PM -0300, Ranier Vilela wrote: > > Sorry, but this is much more on the client side. > > The client is reporting the problem, as is the server. > Are you read the server log? " 2022-03-03 01:04:40 EST

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

On Thu, Mar 03, 2022 at 01:33:08PM -0300, Ranier Vilela wrote: > Sorry, but this is much more on the client side. The client is reporting the problem, as is the server. > Following the logs, it is understood that the client is dropping the > connection. The logs show that the client's

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

> Cc: pgsql-performa...@postgresql.org > > Subject: Re: An I/O error occurred while sending to the backend (PG > 13.4) >> >> On Tue, Mar 01, 2022 at 04:28:31PM +, l...@laurent-hasson.com >> wrote: >> > Now, there is an additional component I

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

> -Original Message- > From: Justin Pryzby > Sent: Tuesday, March 1, 2022 14:27 > To: l...@laurent-hasson.com > Cc: pgsql-performa...@postgresql.org > Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > &g

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

gt; >Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > > > >Em qui., 24 de fev. de 2022 às 09:59, Justin Pryzby pry...@telsasoft.com> escreveu: > >On Thu, Feb 24, 2022 at 08:50:45AM -0300, Ranier Vilela wrote: > >> I can't understand why you a

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

On Tue, Mar 01, 2022 at 04:28:31PM +, l...@laurent-hasson.com wrote: > Now, there is an additional component I think... Storage is on an array and I > am not getting a clear answer as to where it is  Is it possible that > something is happening at the storage layer? Could that be reported

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

> -Original Message- > From: Justin Pryzby > Sent: Monday, February 28, 2022 17:05 > To: l...@laurent-hasson.com > Cc: pgsql-performa...@postgresql.org > Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > &g

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

On Mon, Feb 28, 2022 at 09:43:09PM +, l...@laurent-hasson.com wrote: >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

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

> -Original Message- > From: Justin Pryzby > Sent: Friday, February 25, 2022 08:02 > To: l...@laurent-hasson.com > Cc: pgsql-performa...@postgresql.org > Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > &g

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

>From: Ranier Vilela >Sent: Thursday, February 24, 2022 08:46 >To: Justin Pryzby >Cc: l...@laurent-hasson.com; pgsql-performa...@postgresql.org >Subject: Re: An I/O error occurred while sending to the backend (PG 13.4) > >Em qui., 24 de fev. de 2022 às 09:59, Justin

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

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

Em qui., 24 de fev. de 2022 às 09:59, Justin Pryzby escreveu: > On Thu, Feb 24, 2022 at 08:50:45AM -0300, Ranier Vilela wrote: > > I can't understand why you are still using 13.4? > > [1] There is a long discussion about the issue with 13.4, the project was > > made to fix a DLL bottleneck. > >

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

On Thu, Feb 24, 2022 at 08:50:45AM -0300, Ranier Vilela wrote: > I can't understand why you are still using 13.4? > [1] There is a long discussion about the issue with 13.4, the project was > made to fix a DLL bottleneck. > > Why you not use 13.6? That other problem (and its fix) were in the

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

> Cc: pgsql-performa...@postgresql.org > > Subject: RE: An I/O error occurred while sending to the backend (PG > 13.4) >> >> >> > -Original Message- >> > From: Justin Pryzby >> > Sent: Saturday, Decembe

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

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

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

On Thu, Feb 24, 2022 at 12:47:42AM +, l...@laurent-hasson.com wrote: > On Sat, Dec 04, 2021 at 05:32:10PM +, l...@laurent-hasson.com wrote: > > I have a data warehouse with a fairly complex ETL process that has > > been running for years now across PG 9.6, 11.2 and now 13.4

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

> -Original Message- > From: l...@laurent-hasson.com > Sent: Saturday, December 4, 2021 14:18 > To: Justin Pryzby > Cc: pgsql-performa...@postgresql.org > Subject: RE: An I/O error occurred while sending to th

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

On Sat, Dec 04, 2021 at 07:18:06PM +, l...@laurent-hasson.com wrote: > It's a remote server, but all on a local network. Network performance is I am > sure not the issue. Also, the system is on Windows Server. What are you > expecting to see out of a tcpdump? I'll try to get PG logs on the

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

> -Original Message- > From: Justin Pryzby > Sent: Saturday, December 4, 2021 12:59 > To: l...@laurent-hasson.com > Cc: pgsql-performa...@postgresql.org > Subject: Re: An I/O error occurred while sending to the backend (PG > 13.4) >

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

On Sat, Dec 04, 2021 at 05:32:10PM +, l...@laurent-hasson.com wrote: > I have a data warehouse with a fairly complex ETL process that has been > running for years now across PG 9.6, 11.2 and now 13.4 for the past couple of > months. I have been getting the error "An I/O error occurred while

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

Hello, I hope this email finds you all well! I have a data warehouse with a fairly complex ETL process that has been running for years now across PG 9.6, 11.2 and now 13.4 for the past couple of months. I have been getting the error "An I/O error occurred while sending to the backend" quite