pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Ranier Vilela <ranier.vf@gmail.com>
Cc: 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: Thu, 3 Mar 2022 10:46:04 -0600
Message-ID: <20220303164604.GH27651@telsasoft.com> (raw)
In-Reply-To: <CAEudQAot0tEAkPiVLU38NdQAQx8M0p-LQmRZCVm7jCQDAkBKSA@mail.gmail.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>
	<20220301192641.GA15744@telsasoft.com>
	<MN2PR15MB2560956DE25947E5E944C96785049@MN2PR15MB2560.namprd15.prod.outlook.com>
	<CAEudQAot0tEAkPiVLU38NdQAQx8M0p-LQmRZCVm7jCQDAkBKSA@mail.gmail.com>

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 connection *was* dropped.
And on the server, the same.

> So most likely the error could be from Pentaho or JDBC.
> 
> https://www.geeksforgeeks.org/java-net-socketexception-in-java-with-examples/
> " This *SocketException* occurs on the server-side when the client closed
> the socket connection before the response could be returned over the
> socket."
> 
> I suggest moving this thread to the Pentaho or JDBC support.

We don't know the source of the problem.  I still doubt it's in postgres, but I
don't think it's helpful to blame the client, just because the client reported
the problem.  If the server were to disconnect abruptly, I'd expect the client
to report that, too.

Laurent would just have to start the conversation over (and probably collect
the same diagnostic information anyway).  The client projects could blame
postgres with as much rationale as there is for us to blame the client.

Please don't add confusion here.  I made suggestions for how to collect more
information to better understand the source of the problem, and there's
probably not much else to say without that.

-- 
Justin





view thread (25+ messages)  latest in thread

Message-ID: <20220303164604.GH27651@telsasoft.com>
Permalink:  ../20220303164604.GH27651@telsasoft.com/
Also on:    postgresql.org/message-id/20220303164604.GH27651@telsasoft.com

 · 

reply
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, ranier.vf@gmail.com, ldh@laurent-hasson.com
  Subject: Re: An I/O error occurred while sending to the backend (PG 13.4)
  In-Reply-To: <20220303164604.GH27651@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