Bad pg_dump error message

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Bad pg_dump error message
Date: 2012-09-11 00:27:54
Message-ID: CABs1bs1FQOAcqKbmx2gVqB+JirtZccJ=9ZdkZEC2W0fDbtQVtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

If there's any hard limits (like memory, or RAM) that can be checked
before it spends two hours downloading the data, that might be a
better experience.. I'd be happy to file a bug.. Thanks!!

Mike

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Janes 2012-09-11 02:42:21 Re: Bad pg_dump error message
Previous Message Edson Richter 2012-09-10 23:04:28 Re: Compressed binary field