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: Tue, 1 Mar 2022 13:26:41 -0600
Message-ID: <20220301192641.GA15744@telsasoft.com> (raw)
In-Reply-To: <MN2PR15MB25602F46F8665F53E4E0692F85029@MN2PR15MB2560.namprd15.prod.outlook.com>
References: <20220224020005.GT9008@telsasoft.com>
<20220225130213.GB9008@telsasoft.com>
<MN2PR15MB2560AB0811D016F50044261385019@MN2PR15MB2560.namprd15.prod.outlook.com>
<20220228220503.GF25269@telsasoft.com>
<MN2PR15MB25602F46F8665F53E4E0692F85029@MN2PR15MB2560.namprd15.prod.outlook.com>
On Tue, Mar 01, 2022 at 04:28:31PM +0000, ldh@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 as a network issue vs a storage issue for Postgres?
No. If there were an error with storage, it'd be reported as a local error,
and the query would fail, rather than failing with client-server communication.
> Also, both machines are actually VMs. I forgot to mention that and not sure if that's relevant.
Are they running on the same hypervisor ? Is that hyperv ?
Lacking other good hypotheses, that does seem relevant.
--
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: <20220301192641.GA15744@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