Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aTxMf-0007hk-Ss for pgsql-admin@arkaria.postgresql.org; Thu, 11 Feb 2016 19:57:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aTxMf-0002dA-B8 for pgsql-admin@arkaria.postgresql.org; Thu, 11 Feb 2016 19:57:21 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aTxMe-0002cj-KA for pgsql-admin@postgresql.org; Thu, 11 Feb 2016 19:57:20 +0000 Received: from smtp10.smtpout.orange.fr ([80.12.242.132] helo=smtp.smtpout.orange.fr) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aTxMb-0003FF-Fn for pgsql-admin@postgresql.org; Thu, 11 Feb 2016 19:57:19 +0000 Received: from [192.168.1.32] ([92.136.223.200]) by mwinf5d45 with ME id H7xC1s00A4L2Gqc037xDlU; Thu, 11 Feb 2016 20:57:14 +0100 X-ME-Helo: [192.168.1.32] X-ME-Auth: cGllcnJlLm1hcmllLmNoZXZhbGllckB3YW5hZG9vLmZy X-ME-Date: Thu, 11 Feb 2016 20:57:14 +0100 X-ME-IP: 92.136.223.200 From: =?UTF-8?Q?Pierre_Chevalier_G=c3=a9ologue?= Subject: Re: pg_dump fatal error To: pgsql-admin@postgresql.org References: Message-ID: <56BCE798.1040008@free.fr> Date: Thu, 11 Feb 2016 20:57:12 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Icedove/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -0.9 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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