Re: large database: problems with pg_dump and pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martin Povolny <martin(dot)povolny(at)solnet(dot)cz>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: large database: problems with pg_dump and pg_restore
Date: 2010-10-27 00:13:10
Message-ID: 2634.1288138390@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

=?utf-8?Q?Martin_Povolny?= <martin(dot)povolny(at)solnet(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message mark 2010-10-27 02:41:36 Re: large database: problems with pg_dump and pg_restore
Previous Message Jehan-Guillaume (ioguix) de Rorthais 2010-10-26 22:21:57 Re: large database: problems with pg_dump and pg_restore