Re: v12 and pg_restore -f- - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: v12 and pg_restore -f-
Date
Msg-id CAHE3wgji3u5FxnLQeTDcPqwwfQZmK4W+hA8JdUM-dm5aYHTTMg@mail.gmail.com
Whole thread Raw
In response to Re: v12 and pg_restore -f-  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Em seg., 4 de nov. de 2019 às 11:53, Alvaro Herrera
<alvherre@2ndquadrant.com> escreveu:
>
> On 2019-Oct-17, Tom Lane wrote:
>
> > Stephen Frost <sfrost@snowman.net> writes:
> > > First, I'd like to clarify what I believe Tom's suggestion is, and then
> > > talk through that, as his vote sways this topic pretty heavily.
> >
> > > 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.
>
I'm not.

> > > If you meant for all branches to accept '-f -' and have it go to a './-'
> > > file then that's just a revert of this entire change, which I can't
> > > agree with either
> >
> > 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.
>
+1.


--
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: 64 bit transaction id
Next
From: Julien Rouhaud
Date:
Subject: Re: Collation versioning