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

From Andrew Dunstan
Subject Re: pg_dump additional options for performance
Date
Msg-id 47B069E8.3020303@dunslane.net
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>)
List pgsql-hackers

Alvaro Herrera wrote:
> --multidump-prefix=foobar
> and it creates foobar.1.predata, foobar.2.data, foobar.3.postdata
>
> or something like that?  The number would help to sort them
> appropriately, and the string would ensure that you know what each file
> is ... perhaps we could have %-escapes in the name to expand to both of
> these?  Perhaps we could have other %-escapes for things like database
> name --- so you could say --multidump-filename=%d.%n.%t.dump ... but
> then it would be nice to have strftime escapes too.
>
> Or is this too complex?
>   

Yes, I think it is. We do not have to be infinitely flexible. KISS seems 
apposite.

cheers

andrew




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_dump additional options for performance
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_dump additional options for performance