Re: pg_dump directory archive format / parallel pg_dump - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump directory archive format / parallel pg_dump
Date
Msg-id AANLkTi=pFPJO8E5EkdoJET9jc+yq5c2d3VDqf2d9e6Qt@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump directory archive format / parallel pg_dump  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: pg_dump directory archive format / parallel pg_dump  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, Jan 21, 2011 at 4:41 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> There's one UI thing that bothers me. The option to specify the target
> directory is called --file. But it's clearly not a file. OTOH, I'd hate to
> introduce a parallel --dir option just for this. Any thoughts on this?

If we were starting over, I'd probably suggest calling the option -o,
--output.  But since -o is already taken (for --oids) I'd be inclined
to just make the help text read:
 -f, --file=FILENAME         output file (or directory) name -F, --format=c|t|p|d        output file format (custom,
tar,text, dir)
 

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Sync Rep for 2011CF1
Next
From: "Kevin Grittner"
Date:
Subject: Re: SSI and Hot Standby