Re: Modified pg_dump & new pg_restore need testing... - Mailing list pgsql-hackers

From Philip Warner
Subject Re: Modified pg_dump & new pg_restore need testing...
Date
Msg-id 3.0.5.32.20000701231033.02181c80@mail.rhyme.com.au
Whole thread Raw
In response to Modified pg_dump & new pg_restore need testing...  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: Modified pg_dump & new pg_restore need testing...  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
At 13:53 30/06/00 -0300, The Hermit Hacker wrote:
>
>Sounds like something that is a suitable replacement for what we have now
>... I particularly like the 'compressed output' *but* is there some way,
>for the paranoid, of doing an uncompressed format
>(--dont-compress?)?  Then again, how does this handle someone wanting to
>dump the database for reloading into a non-PgSQL database?  
>

As suggested I have now added a '--plain-text, -p' option to pg_dump to
dump it into text. Needless to say the output can not be used by pg_restore
(although, I suppose, it is feasible). This also supports the -Z flag, to
dump in gzip format.






----------------------------------------------------------------
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-hackers by date:

Previous
From: Oleg Broytmann
Date:
Subject: Re: Built with PostgreSQL (images)
Next
From: Peter Eisentraut
Date:
Subject: Bug in new memory system?