Re: pg_dump additional options for performance

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "Decibel!" <decibel(at)decibel(dot)org>, Zeugswetter Andreas ADI SD <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump additional options for performance
Date: 2008-02-11 17:42:46
Message-ID: 47B08916.60605@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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.
>
>
>

this looks good. But arguably it's really pre-data and post-data.
pre-schema would be something that comes before the schema, no? Or maybe
it should be {pre,post}-data-schema-file.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-02-11 17:46:28 Re: pg_dump additional options for performance
Previous Message Claudio Rossi 2008-02-11 17:39:32 Re: Truncate Triggers