Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 02319133798E for ; Tue, 26 Oct 2010 21:13:18 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 04913-08 for ; Wed, 27 Oct 2010 00:13:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 591611336DB6 for ; Tue, 26 Oct 2010 21:13:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o9R0DA6U002635; Tue, 26 Oct 2010 20:13:10 -0400 (EDT) To: =?utf-8?Q?Martin_Povolny?= cc: pgsql-admin@postgresql.org Subject: Re: =?utf-8?Q?large_database=3A_problems_with_pg=5Fdump_and_pg=5Frestore?= In-reply-to: References: Comments: In-reply-to =?utf-8?Q?Martin_Povolny?= message dated "Tue, 26 Oct 2010 13:41:44 +0200" Date: Tue, 26 Oct 2010 20:13:10 -0400 Message-ID: <2634.1288138390@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201010/192 X-Sequence-Number: 35933 =?utf-8?Q?Martin_Povolny?= writes: > I had 5 databases, 4 dumped ok, the 5th, the largest failed dumping: I was unable to > make a dump in the default 'tar' format. I got this message: > pg_dump: [tar archiver] archive member too large for tar format This is expected: tar format has a documented limit of 8GB per table. (BTW, tar is not the "default" nor the recommended format, in part because of that limitation. The custom format is preferred unless you really *need* to manipulate the dump files with "tar" for some reason.) > for the bb.dump in the 'custom' format: > pg_restore: [vlastní archivář] unexpected end of file Hm, that's weird. I can't think of any explanation other than the dump file somehow getting corrupted. Do you get sane-looking output if you run "pg_restore -l bb.dump"? regards, tom lane