pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pierre Chevalier Géologue <pierrechevaliergeol@free.fr>
To: pgsql-admin@postgresql.org
Subject: Re: pg_dump fatal error
Date: Thu, 11 Feb 2016 20:57:12 +0100
Message-ID: <56BCE798.1040008@free.fr> (raw)
In-Reply-To: <CAE_gQfXD622Uv0o2N5fmbBTbEDH7=-0TWeRwYjXEUQXJo7bs_Q@mail.gmail.com>
References: <CAE_gQfXD622Uv0o2N5fmbBTbEDH7=-0TWeRwYjXEUQXJo7bs_Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

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
____________________________________________________________________________


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (8+ messages)  latest in thread

Message-ID: <56BCE798.1040008@free.fr>
Permalink:  ../56BCE798.1040008@free.fr/
Also on:    postgresql.org/message-id/56BCE798.1040008@free.fr

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: pierrechevaliergeol@free.fr
  Subject: Re: pg_dump fatal error
  In-Reply-To: <56BCE798.1040008@free.fr>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox