Re: [GENERAL] Bad pg_dump error message

2012-09-17 Thread Jasen Betts
On 2012-09-11, Mike Christensen m...@kitchenpc.com wrote: Is the TAR format just the raw SQL commands, just tar'ed and then sent over the wire? It'd be cool if there was some compressed binary backup of a database that could be easily downloaded, or even better, a way to just move an entire

Re: [GENERAL] Bad pg_dump error message

2012-09-11 Thread Peter Eisentraut
On Tue, 2012-09-11 at 01:21 -0400, Tom Lane wrote: Mike Christensen m...@kitchenpc.com writes: Oh reading the online docs, it looks like what I may have wanted was: --format=custom Right. That does everything tar format does, only better --- the only thing tar format beats it at is you

Re: [GENERAL] Bad pg_dump error message

2012-09-11 Thread Tom Lane
Peter Eisentraut pete...@gmx.net writes: We could change the tar code to produce POSIX 2001 format archives, which don't have that limitation. But if someone wanted to do some work in this area, it might be more useful to look into a zip-based format. I find it doubtful that it's worth

[GENERAL] Bad pg_dump error message

2012-09-10 Thread Mike Christensen
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

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Jeff Janes
On Mon, Sep 10, 2012 at 5:27 PM, Mike Christensen m...@kitchenpc.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

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Tom Lane
Jeff Janes jeff.ja...@gmail.com writes: On Mon, Sep 10, 2012 at 5:27 PM, Mike Christensen m...@kitchenpc.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

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Mike Christensen
On Mon, Sep 10, 2012 at 9:57 PM, Tom Lane t...@sss.pgh.pa.us wrote: Jeff Janes jeff.ja...@gmail.com writes: On Mon, Sep 10, 2012 at 5:27 PM, Mike Christensen m...@kitchenpc.com wrote: Is there something that can be done smarter with this error message? pg_dump: dumping contents of table pages

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Mike Christensen
On Mon, Sep 10, 2012 at 10:06 PM, Mike Christensen m...@kitchenpc.com wrote: On Mon, Sep 10, 2012 at 9:57 PM, Tom Lane t...@sss.pgh.pa.us wrote: Jeff Janes jeff.ja...@gmail.com writes: On Mon, Sep 10, 2012 at 5:27 PM, Mike Christensen m...@kitchenpc.com wrote: Is there something that can be

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Tom Lane
Mike Christensen m...@kitchenpc.com writes: Oh reading the online docs, it looks like what I may have wanted was: --format=custom Right. That does everything tar format does, only better --- the only thing tar format beats it at is you can disassemble it with tar. Back in the day that seemed

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Tom Lane
Mike Christensen m...@kitchenpc.com writes: Is the TAR format just the raw SQL commands, just tar'ed and then sent over the wire? Sorta. If you pull it apart with tar, you'll find out there's a SQL script that creates the database schema, and then a separate tar-member file containing the data

Re: [GENERAL] Bad pg_dump error message

2012-09-10 Thread Mike Christensen
On Mon, Sep 10, 2012 at 10:21 PM, Tom Lane t...@sss.pgh.pa.us wrote: Mike Christensen m...@kitchenpc.com writes: Oh reading the online docs, it looks like what I may have wanted was: --format=custom Right. That does everything tar format does, only better --- the only thing tar format beats