Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP893-0000CD-NQ for pgsql-performance@arkaria.postgresql.org; Tue, 01 Mar 2022 19:26:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nP892-0006Q0-7n for pgsql-performance@arkaria.postgresql.org; Tue, 01 Mar 2022 19:26:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP891-0006Pr-Rm for pgsql-performance@lists.postgresql.org; Tue, 01 Mar 2022 19:26:47 +0000 Received: from mail-io1-xd31.google.com ([2607:f8b0:4864:20::d31]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nP88y-0002HX-Qy for pgsql-performance@postgresql.org; Tue, 01 Mar 2022 19:26:47 +0000 Received: by mail-io1-xd31.google.com with SMTP id d62so19627483iog.13 for ; Tue, 01 Mar 2022 11:26:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=0mFbMTPImtLvwDOg2lZEHe7VAraKvSk8P0iZ22rzXE0=; b=brQQ4tJXlUY9mSFqp6Dbi8rRQg/UgjSlpMhiN2wR1PAsCQPnkEaoNbOtik8kTOJgoE ORvFxSACIAzfMaoeDWhgkLwPU59VXVt7YjqOJOobZjCVzAKYBQMDo11xid4+mCGC/Rn4 YIQZXxjed2+i9u8n90xSuubR/Zrl4x9Lct4UeSXA0B0fTtsle0Ir4VuvWW1OsQE086KE 6VmQb8P7+28nRa1QPYgyishMBJaS7YOJrgeMhaoNlD2Dj5Bz6+c9igKeJsNrsqb7hbI2 bL2rwuOokyyq2vKLwnscVBQwzFk8rZooyOWrOIBmNZzNmUAG8fXAe9jI9/J82tIEgfnM 4f8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=0mFbMTPImtLvwDOg2lZEHe7VAraKvSk8P0iZ22rzXE0=; b=jbjIK1eyBtIjrpRw4K55hoQcnIQr24HlhTac03D9mK/5qIDoVqSsNM6zAy7VNOxWs3 Xh9W5OwJBJoNvq8T3dVvQv6OKgX1gZvUwYhZAWwhyw99HNkmwDmziRx8GSyj+cOg3/fe YKZSCchJdLx9Je2KtpctOG84SgUcRkmkeZi+bOmsnRlMyZreYS08n9kMVPwKu2K8zhIE /uYEN0r5nRpgkB9qNCW4aXRvdUkdrl3ODCWo3/kFMyqtLAHpi+8mNByiflzAC/caHK1n aFWV7MXPUWcP3yh2EnXnGkEYXMHiAFAEOZQZg7bPZZ4fm0sbv+NJcDFeKLM4AaFXv8TS i22w== X-Gm-Message-State: AOAM530TmFiQVDVpopLBOUY4FS7u6NczKtWnOaxXk0pjHa/AF9D3SUfL 0BWujA/3nDczVcMwzHVsTalZaw== X-Google-Smtp-Source: ABdhPJznqt83bmJhp3BU5fMznXJfOETEgZHoeaMvuIjuySGEtDi39D+XNEMspHAgGl+Gow6JG4rkqg== X-Received: by 2002:a6b:8ed2:0:b0:641:3d13:47ad with SMTP id q201-20020a6b8ed2000000b006413d1347admr20151045iod.168.1646162803061; Tue, 01 Mar 2022 11:26:43 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id n1-20020a92d9c1000000b002c26b97c8dasm8081814ilq.35.2022.03.01.11.26.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Mar 2022 11:26:42 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 9E64D800E22; Tue, 1 Mar 2022 13:26:41 -0600 (CST) Date: Tue, 1 Mar 2022 13:26:41 -0600 From: Justin Pryzby 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) Message-ID: <20220301192641.GA15744@telsasoft.com> References: <20220224020005.GT9008@telsasoft.com> <20220225130213.GB9008@telsasoft.com> <20220228220503.GF25269@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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