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

From Tom Lane
Subject Re: pg_dump additional options for performance
Date
Msg-id 2816.1202748667@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump additional options for performance  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pg_dump additional options for performance  (Simon Riggs <simon@2ndquadrant.com>)
Re: pg_dump additional options for performance  (Andrew Dunstan <andrew@dunslane.net>)
Re: pg_dump additional options for performance  ("Jochem van Dieten" <jochemd@gmail.com>)
List pgsql-hackers
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.
        regards, tom lane


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