Re: pg_dump fatal error

From: "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump fatal error
Date: 2016-02-11 18:33:22
Message-ID: CAE_gQfWzm_UjXbP1VvHRxKnMadp-NT_bM9M_9vZst9jkSs60CQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

ERROR: unexpected message type 0x58 during COPY from stdin
On 12 February 2016 at 07:30, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com>
wrote:

> Hi guys
>
> I'm doing a copy (pg_dump) from a slave server to a test server.
> The DB size is 1,7 TB, and I get the error at 1,4 TB.
>
> Command:
>
>> ssh postgres(at)servidorslave01 "/usr/pgsql-9.2/bin/pg_dump
>> --exclude-table-data='junk.*' --format=custom db_live"
>> | /usr/pgsql-9.2/bin/pg_restore --dbname=uat_temp --exit-on-error
>
>
> Error:
>
>> |postgres|pg_restore| CONTEXT: COPY ja_feedlog, line 1
>> STATEMENT: COPY ja_feedlog (id, clientid, mobiuserid, customerid,
>> invoiceid, description, gtime, jobid, log_type, serialised_data,
>> push_status, requestorid, the_geom, admin_read, visitid) FROM stdin;
>
>
> LOG: could not send data to client: Broken pipe
>> FATAL: connection to client lost
>
>
> What can cause that kind of error? I've tried more than once, actually.
>
> Thanks
> Lucas
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2016-02-11 18:52:30 Re: pg_dump fatal error
Previous Message drum.lucas@gmail.com 2016-02-11 18:30:21 pg_dump fatal error