Re: pg_dump - Mailing list pgsql-hackers

From Philip Warner
Subject Re: pg_dump
Date
Msg-id 3.0.5.32.20010425120443.02d6a820@mail.rhyme.com.au
Whole thread Raw
In response to pg_dump  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: pg_dump  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
At 10:00 25/04/01 +0900, Tatsuo Ishii wrote:
>Does anybody know:
>
>1) Is the tar/custom format of pg_dump is portable accross different
>   platforms?

It's supposed to be; if it's not, it's a bug.


>2) if I want to dump out all of database cluster contents including
>   large objects, is following procedure correct?
>
>   (dump procedure)
>   pg_dumpall -g
>   pg_dump -F c .... for each database
>       :
>       :
>
>   (restore procedure)
>   initdb
>   psql template1 < dumpout_of_pg_dumpall
>   pg_restore ... for each database

Looks OK to me. You need a '-b' on the pg_dump (for BLOBS), and each dump
command will need to go to a separate file - it won't currently work if
multiple dumps are being sent to stdout.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 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: Tatsuo Ishii
Date:
Subject: pg_dump
Next
From: Lincoln Yeoh
Date:
Subject: Re: Re: refusing connections based on load ...