Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly"
| От | Tom Lane |
|---|---|
| Тема | Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly" |
| Дата | |
| Msg-id | 6065.1442933960@sss.pgh.pa.us обсуждение |
| Ответ на | pg_dump - postgre 9.2 and "server closed the connection unexpectedly" (Maycon Oliveira <fuinhaazul@gmail.com>) |
| Ответы |
Re: pg_dump - postgre 9.2 and "server closed the connection
unexpectedly"
|
| Список | 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 по дате отправления: