Re: -f <output file> option for pg_dumpall

> ------- Original Message -------
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: Dave Page <dpage(at)postgresql(dot)org>
> Sent: 1/5/07, 10:52:37 PM
> Subject: Re: [HACKERS] -f <output file> option for pg_dumpall
>
> I think this will be an exercise in time-wasting, and very possibly
> destabilize *both* tools. pg_dump has never been designed to reconnect
> to a different database; for instance there isn't any code for resetting
> all the internal state that it gathers. I think forking a separate
> pg_dump for each database is a perfectly fine arrangement, and should be
> left alone.

Hmm, would you be happy with my original proposal to add an append option to pg_dump?

I'd also like to allow separate dumping of roles and tablespaces, and allow a default db to be specified instead of postgres/template1.

/D