Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly" - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly"
Date
Msg-id 6065.1442933960@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump - postgre 9.2 and "server closed the connection unexpectedly"  (Maycon Oliveira <fuinhaazul@gmail.com>)
Responses Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly"
List pgsql-general
Maycon Oliveira <fuinhaazul@gmail.com> writes:
> i´m using postgre for 2 years now and i started to have this *INTERMITENT*
> error from pg_dump:
> pg_dump: Dumping the contents of table "adm_log" failed: PQgetCopyData()
> failed.
> pg_dump: Error message from server: server closed the connection
> unexpectedly

> Looking on the postgre logs i see this error:
> LOG:  could not send data to client: Connection timed out
> STATEMENT:  COPY xcp0000000001.adm_log (seq_log, dth_evento, des_mensagem,
> des_usuario, des_objeto) TO stdout;

Evidently a connectivity problem, not a database integrity problem.

Is pg_dump running on a different machine than the server?  If so
you could be looking at network hardware issues.

Is pg_dump using an SSL-encrypted connection?  If so maybe it's a
renegotiation problem.  Try setting ssl_renegotiation_limit = 0
in the server's configuration.

            regards, tom lane


pgsql-general by date:

Previous
From: "Karsten Hilbert"
Date:
Subject: Re: md5(large_object_id)
Next
From: Michael Zoet
Date:
Subject: Re: how to show time zone with numerical offset in CSV log?