Re: -f option for pg_dumpall - Mailing list pgsql-hackers

From Dave Page
Subject Re: -f option for pg_dumpall
Date
Msg-id 200701060855190000@2879532645
Whole thread Raw
In response to -f option for pg_dumpall  (Dave Page <dpage@postgresql.org>)
Responses Re: -f option for pg_dumpall
List pgsql-hackers

> ------- Original Message -------
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: Dave Page <dpage@postgresql.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




pgsql-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: -f option for pg_dumpall
Next
From: Oleg Bartunov
Date:
Subject: Re: PGCon 2007 Program Committee