=?utf-8?Q?Martin_Povolny?= <martin.povo...@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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
