Re: large database: problems with pg_dump and pg_restore - Mailing list pgsql-admin

From Tom Lane
Subject Re: large database: problems with pg_dump and pg_restore
Date
Msg-id 2634.1288138390@sss.pgh.pa.us
Whole thread Raw
In response to large database: problems with pg_dump and pg_restore  (Martin Povolny <martin.povolny@solnet.cz>)
Responses Re: [ADMIN] large database: problems with pg_dump and pg_restore
List pgsql-admin
=?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


pgsql-admin by date:

Previous
From: "Jehan-Guillaume (ioguix) de Rorthais"
Date:
Subject: Re: large database: problems with pg_dump and pg_restore
Next
From: "mark"
Date:
Subject: Re: large database: problems with pg_dump and pg_restore