Re: pg_dump fatal error

From: Pierre Chevalier Géologue <pierrechevaliergeol(at)free(dot)fr>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump fatal error
Date: 2016-02-11 19:57:12
Message-ID: 56BCE798.1040008@free.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello,

What about trying to use a temporary file?

Le 11/02/2016 19:30, drum(dot)lucas(at)gmail(dot)com a écrit :
> 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
>

Something like:

ssh postgres(at)servidorslave01
/usr/pgsql-9.2/bin/pg_dump --exclude-table-data='junk.*' --format=custom
db_live > bigdump
/usr/pgsql-9.2/bin/pg_restore --dbname=uat_temp --exit-on-error bigdump

(no guarantee at all, I'm just blindly guessing!)

I usually do pg_dump's using plain SQL format: this allows to debug such
nasty surprises. It sometimes helps. In your case, I would do
something like:

ssh postgres(at)servidorslave01
/usr/pgsql-9.2/bin/pg_dump --exclude-table-data='junk.*' > bigdump.sql
# just to have a look at the dump:
less bigdump.sql
/usr/pgsql-9.2/bin/psql --dbname=uat_temp -f bigdump

À+
Pierre
--
____________________________________________________________________________
Pierre Chevalier
PChGEI: Pierre Chevalier Géologue Et Informaticien
Mesté Duran
32100 Condom
Tél+fax : 09 75 27 45 62
06 37 80 33 64
Émail : pierrechevaliergeolCHEZfree.fr
icq# : 10432285
jabber: pierre(dot)chevalier1967(at)jabber(dot)fr
http://pierremariechevalier.free.fr/pierre_chevalier_geologue
____________________________________________________________________________

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Pierre Chevalier Géologue 2016-02-12 09:08:24 Re: pg_dump fatal error
Previous Message drum.lucas@gmail.com 2016-02-11 19:11:18 Re: pg_dump fatal error