Re: Bad pg_dump error message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Mike Christensen <mike(at)kitchenpc(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Bad pg_dump error message
Date: 2012-09-11 04:57:52
Message-ID: 10269.1347339472@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Mon, Sep 10, 2012 at 5:27 PM, Mike Christensen <mike(at)kitchenpc(dot)com> wrote:
>> Is there something that can be done smarter with this error message?
>>
>> pg_dump: dumping contents of table pages
>> pg_dump: [tar archiver] archive member too large for tar format
>> pg_dump: *** aborted because of error

> There is no efficient way for it to know for certain in advance how
> much space the data will take, until it has seen the data. Perhaps it
> could make an estimate, but that could suffer from both false
> positives and false negatives.

Maybe the docs should warn people away from tar format more vigorously.
Unless you actually have a reason to disassemble the archive with tar,
that format has no redeeming social value that I can see, and it
definitely has gotchas. (This isn't the only one, IIRC.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Christensen 2012-09-11 05:06:53 Re: Bad pg_dump error message
Previous Message Mike Christensen 2012-09-11 04:43:16 Where do I get pgAdmin 1.16 for openSuSE?