Re: v12 and pg_restore -f-

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
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 15:05:09
Message-ID: 6692.1572879909@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-Oct-17, Tom Lane wrote:
>> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>>> Tom, I take it your suggestion is to have '-f -' be accepted to mean
>>> 'goes to stdout' in all branches?

>> Yes.

> +1 for this, FWIW. Let's get it done before next week minors. Is
> anybody writing a patch? If not, I can do it.

Please do.

>> No, I'm not proposing a full revert. But there's certainly room to
>> consider reverting the part that says you *must* write "-f -" to get
>> output to stdout.

> I don't think this will buy us anything, if we get past branches updated
> promptly.

I'm okay with that approach.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Euler Taveira 2019-11-04 15:14:09 Re: v12 and pg_restore -f-
Previous Message Ravi Krishna 2019-11-04 15:00:27 Re: explain plan difference

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-11-04 15:07:23 Re: 64 bit transaction id
Previous Message Tom Lane 2019-11-04 15:01:25 Re: alternative to PG_CATCH