Date: Mon, 4 Nov 2019 16:43:05 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>,
	"imai.yoshikazu@fujitsu.com" <imai.yoshikazu@fujitsu.com>,
	Euler Taveira <euler@timbira.com.br>,
	Andrew Gierth <andrew@tao11.riddles.org.uk>,
	Justin Pryzby <pryzby@telsasoft.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: v12 and pg_restore -f-
Message-ID: <20191104194305.GA31740@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <25226.1572895469@sss.pgh.pa.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2019-Nov-04, Tom Lane wrote:

> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > Turns out that this is a simple partial cherry-pick of the original
> > commit.
> 
> In the back branches, you should keep the statement that stdout
> is the default output file.  Looks sane otherwise (I didn't test it).

I propose this:

       <para>
        Specify output file for generated script, or for the listing
        when used with <option>-l</option>. Use <literal>-</literal>
        for the standard output, which is also the default.
       </para>

Less invasive formulations sound repetitive (such as "Use - for stdout.
The default is stdout").  I'm open to suggestions.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services