Em qui., 3 de mar. de 2022 às 13:46, Justin Pryzby <pryzby@telsasoft.com> 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 [21228] LOG: could not receive data from client: An existing connection was forcibly closed by the remote host. 2022-03-03 01:04:40 EST [21228] LOG: unexpected EOF on client connection with an open transaction"
> 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.
No, the log server shows that the client dropped the connection.
> 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.
Yeah, but it is much more likely to be on the client.
I still doubt it's in postgres,
Everything indicates not.
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.
