Re: pg_dump additional options for performance
| От | Tom Lane |
|---|---|
| Тема | Re: pg_dump additional options for performance |
| Дата | |
| Msg-id | 2816.1202748667@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: pg_dump additional options for performance (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: pg_dump additional options for performance
Re: pg_dump additional options for performance Re: pg_dump additional options for performance |
| Список | 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 по дате отправления: