At 02:00 AM 16/03/2004, Tom Lane wrote:
> >> Why is there no custom format dump option for pg_dumpall?
>
> > I think it is because we have no mechanism to merge multiple custom
> > format files from different databases into a single file.
That was the main reason (and as Tom suggested, dumpall was a shell script
at the time).
> Perhaps this
> > is a TODO.
>
>but offhand I see no fundamental obstacle
>now that pg_dumpall is a C program.
I agree.
>I'm envisioning
>some super-archive format in which there are individual entries
>containing the pg_dump output for each database
Not sure about this. I'd be inclined to investigate just adding another
attribute to each TOC entry (database_name).
>This does seem like a nice solution to the perennial problem of dumping
>blobs easily.
What is this?
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp.mit.edu:11371 |/