From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Maycon Oliveira <fuinhaazul(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly" |
Date: | 2015-09-22 14:59:20 |
Message-ID: | 6065.1442933960@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Maycon Oliveira <fuinhaazul(at)gmail(dot)com> writes:
> im 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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Zoet | 2015-09-22 15:05:21 | Re: how to show time zone with numerical offset in CSV log? |
Previous Message | Karsten Hilbert | 2015-09-22 14:53:44 | Re: md5(large_object_id) |