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 1nNaEs-000205-1A for pgsql-performance@arkaria.postgresql.org; Fri, 25 Feb 2022 13:02:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nNaEq-0007bO-M8 for pgsql-performance@arkaria.postgresql.org; Fri, 25 Feb 2022 13:02:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNaEq-0007bF-8Y for pgsql-performance@lists.postgresql.org; Fri, 25 Feb 2022 13:02:24 +0000 Received: from mail-io1-xd2d.google.com ([2607:f8b0:4864:20::d2d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nNaEi-0002eL-Bt for pgsql-performance@postgresql.org; Fri, 25 Feb 2022 13:02:22 +0000 Received: by mail-io1-xd2d.google.com with SMTP id c23so6392234ioi.4 for ; Fri, 25 Feb 2022 05:02:16 -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:mime-version:content-disposition :in-reply-to:user-agent; bh=rguk5SSH0foPhPGo8rwFvAZRA/xbEE9AhmUAjrdMujk=; b=jECg60JSfNCYdVq9tB3KAlWkX37ubzXYR5eBG3oljU9dmx0J4VU5Qj3KVNF1K6aQ5E rCQWC4b3uAJK9gYig9qA9eU19lVM9khyFlvoCQ8jiGRx7bSuWuG1pKXtiK55t30aPH7l fVxfzwE22k5/0U5TDXmnV2m0M/uDqHur3TuWJ1Um3DunEu/ve6QQzcDjCnB/9YvGYjJB hfdqdOHBB7d+yLbYJ8Tq2V/kG6HZl36UZR8CO29Cp2hmwcXWN45VRqKUuFz7asDSTZvL ZPga32weyX0bqtwBkBc3vWNsqlYRWVEHnnE3HAtG+JW1r9twlt4BdA4PHU1uXNFnoO8j dBRg== 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:mime-version :content-disposition:in-reply-to:user-agent; bh=rguk5SSH0foPhPGo8rwFvAZRA/xbEE9AhmUAjrdMujk=; b=QYlR/ZOGTnQ6HnYO95BFinGzcs7lnI+s6m9aijx7Bq/joGtEMtHBu0+v991p2VigOE gDicKcQK2McsjSw7F5yBv/YevNcMlCAAJQ3hzYiR1RIvduUyL8SZM1mBF4OwaZAp4aKx W94u54sMnUE5qK2YjZGF+OeiiRvdk7kv9wu3LdzwShSsMzDQQfshWhFUpzD3jR5dc7AA EVOOK/D5DsLpa7U/7uRgBIVvmylA31fYi8PoY4mgakYB4bCLYpVeA3O6Auca11sHbdkT 9sACWc+IQe5jMQMqlcWOCWAsxHVD1C3ZbjUVnBvOfYfCfc51Xwn5J1DHtKKNYwUnKjza XWJw== X-Gm-Message-State: AOAM532YyUVSrUOZo0e89JbYxPnhWolgYU3giePaBWf41pDVQd7R8clG 5rsfn9IsSuYldoNg7bnCdRCI0pyyba6Zfg== X-Google-Smtp-Source: ABdhPJxh97c8hTgYNjKkZxlDy7Oi9vTvfhD9P3NDfYHm+ugAd+6sMLayisqvg3peA143HnffSa4qeA== X-Received: by 2002:a02:ccce:0:b0:315:2ba2:7ce4 with SMTP id k14-20020a02ccce000000b003152ba27ce4mr5736232jaq.28.1645794134599; Fri, 25 Feb 2022 05:02:14 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id q6-20020a92c006000000b002b8647ea375sm1509504ild.67.2022.02.25.05.02.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Feb 2022 05:02:14 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 594FE800559; Fri, 25 Feb 2022 07:02:13 -0600 (CST) Date: Fri, 25 Feb 2022 07:02:13 -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: <20220225130213.GB9008@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220224020005.GT9008@telsasoft.com> 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 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