From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: -f <output file> option for pg_dumpall |
Date: | 2007-01-05 20:03:33 |
Message-ID: | 459EAF15.7010000@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter wrote:
>> This seems a bit like piecemeal reform. Here are some things I'd like to
>> see that affect this area:
>>
>> . merge pg_dump and pg_dumpall (e.g. add a flag to pg_dump that says do
>> the lot)
>> . multi-db non-text dumps
>>
>> And while we're about it, can we teach pg_restore to handle text dumps?
>> Even if it just transparently called psql it would be nice.
>
> +1 on all of this :)
Hmm, well I have no interest in the latter at present, but assuming the
powers that be will allow me some time to do so, I will look at merging
pg_dump and pg_dumpall as that seems to be the way people want to go.
I'd also like to tweak the options for global objects to allow roles and
tablespaces to be dumped seperately from each other if no-one objects.
> Cheers,
> D (who can contribute code once we've agreed on what it should do)
Cool - fancy picking up the multi-db non text and pg_restore bits if I
do the former?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-01-05 20:05:26 | Re: -f <output file> option for pg_dumpall |
Previous Message | Gurjeet Singh | 2007-01-05 19:57:37 | Re: A patch to pg_regress for Windows port |