From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Povolny <martin.povolny@solnet.cz>
Cc: pgsql-admin@postgresql.org
Subject: Re: large database: problems with pg_dump and pg_restore
Date: Tue, 26 Oct 2010 20:13:10 -0400
Message-ID: <2634.1288138390@sss.pgh.pa.us> (raw)
In-Reply-To: <E1PAhuU-0006Fa-DI@ns.solnet.cz>
References: <E1PAhuU-0006Fa-DI@ns.solnet.cz>
=?utf-8?Q?Martin_Povolny?= <martin.povolny@solnet.cz> 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
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: tgl@sss.pgh.pa.us, martin.povolny@solnet.cz
Subject: Re: large database: problems with pg_dump and pg_restore
In-Reply-To: <2634.1288138390@sss.pgh.pa.us>
* 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