Re: pg_dump fatal error

Hello,

What about trying to use a temporary file?

Le 11/02/2016 19:30, drum.lucas@gmail.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@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@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@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.chevalier1967@jabber.fr
   http://pierremariechevalier.free.fr/pierre_chevalier_geologue
____________________________________________________________________________