From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, "imai(dot)yoshikazu(at)fujitsu(dot)com" <imai(dot)yoshikazu(at)fujitsu(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: v12 and pg_restore -f- |
Date: | 2019-11-04 19:43:05 |
Message-ID: | 20191104194305.GA31740@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 2019-Nov-04, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-11-04 19:44:19 | Re: v12 and pg_restore -f- |
Previous Message | Euler Taveira | 2019-11-04 19:35:03 | Re: v12 and pg_restore -f- |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-11-04 19:44:19 | Re: v12 and pg_restore -f- |
Previous Message | Andres Freund | 2019-11-04 19:42:24 | Re: cost based vacuum (parallel) |