Re: RE: [HACKERS] pg_dump & blobs - editable dump? - Mailing list pgsql-general

From Philip Warner
Subject Re: RE: [HACKERS] pg_dump & blobs - editable dump?
Date
Msg-id 3.0.5.32.20000713105806.0267e500@mail.rhyme.com.au
Whole thread Raw
In response to Re: RE: [HACKERS] pg_dump & blobs - editable dump?  (Giles Lean <giles@nemeton.com.au>)
List pgsql-general
At 07:58 13/07/00 +1000, Giles Lean wrote:
>
>I recommend you compress the whole stream, not the pieces.  Presumably
>you can determine the size of the pieces you're backing up, and ending
>with a .tar.gz (or whatever) file is more convenient to manage than a
>.tar file of compressed pieces unless you really expect people to be
>extracting individual files from the backup very often.
>
>Having to pass everything through /tmp would be really unfortunate.
>

The only things I compress are the table data and the blobs (ie. the big
things); unfortunately, the table data is of unknown uncompressed size. I
*could* do two 'COPY TO STDOUT' calls, just to get the size, but that seems
like a very bad idea.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.C.N. 008 659 498)             |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|
                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Figured it out (psql and Gnu readline)
Next
From: Erich
Date:
Subject: Re: Figured it out (psql and Gnu readline)