Re: pg_dump additional options for performance - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_dump additional options for performance
Date
Msg-id 47B082A7.2040300@hagander.net
Whole thread Raw
In response to Re: pg_dump additional options for performance  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: pg_dump additional options for performance  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> On Mon, 2008-02-11 at 11:51 -0500, Tom Lane wrote:
>> Alvaro Herrera <alvherre@commandprompt.com> writes:
>>> I think this is pretty unwieldy.
>> I agree.  Since any multiple-output-file case can't usefully use stdout,
>> I think we should combine the switches and just have one switch that
>> says both that you want separated output and what the target filename
>> is.  Thus something like
>>
>>     --pre-schema-file = foo
>>     --data-file = bar
>>     --post-schema-file = baz
>>
>> where specifying any of these suppresses the "normal" output to stdout.
>> So, if you give just a subset of them, you get just subset output.
>>
>> With this design, --schema-only, --data-only, and --file are obsolete,
>> and we should probably throw an error if any of them are used in
>> combination with these switches.
> 
> Looks good from here.

+1

Simon, are you planning to do this? (assuming everybody agrees on the 
syntax)

//Magnus


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pg_dump additional options for performance
Next
From: Simon Riggs
Date:
Subject: Re: pg_dump additional options for performance