Tomas Vondra writes:
> On 11/23/2017 01:25 AM, Neto pr wrote:
>> Anyone have any tips on why this occurs?
> Attach gdb to the backend, run the query and when it fails get us the
> backtrace. So something like
More details on that here:
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_o
On 11/23/2017 01:25 AM, Neto pr wrote:
> Another fact is that when executing the query without the command
> EXPLAIN ANALYZE, the result is usually returned after a few minutes.
> I do not understand, because when using the EXPLAIN ANALYZE command the
> dbms closes the connection.
> Anyone have a
Another fact is that when executing the query without the command EXPLAIN
ANALYZE, the result is usually returned after a few minutes.
I do not understand, because when using the EXPLAIN ANALYZE command the
dbms closes the connection.
Anyone have any tips on why this occurs?
2017-11-22 21:19 GMT-0
Only complementing
I use postgresql version 10.
However the postgresql.conf file has standard settings.
My server is a 2.8 GHz Xeon (4 core) and SSDs disc.
2017-11-22 21:12 GMT-03:00 Neto pr :
> Dear all,
> when executing a query, it causes the database to close the connection.
> See the error re
Dear all,
when executing a query, it causes the database to close the connection.
See the error reported by the SQL TOOL DBEAVER tool:
- DBEAVER SQL tool-
An I / O error occurred while sending to the backend.
java.io.EOFException:
---
