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

From Tom Lane
Subject Re: v12 and pg_restore -f-
Date
Msg-id 7897.1572964109@sss.pgh.pa.us
Whole thread Raw
In response to Re: v12 and pg_restore -f-  (Stephen Frost <sfrost@snowman.net>)
Responses Re: v12 and pg_restore -f-
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
>> On 2019-11-04 15:53, Alvaro Herrera wrote:
>>>> 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 think we should revert the part that requires using -f - at least for
>> PG12.

> Absolutely not.  This argument could be made, with a great deal more
> justification, against the changes to remove recovery.conf, and I'm sure
> quite a few other changes that we've made between major versions over
> the years, but to do so would be to hamstring our ability to make
> progress and to improve PG.

In this case, not in the least: we would simply be imposing the sort
of *orderly* feature introduction that I thought was the plan from
the very beginning [1].  That is, first make "-f -" available, and
make it required only in some later version.  If we'd back-patched
the optional feature back in April, it might've been okay to require
it in v12, but we failed to provide any transition period.

I'm in favor of making v12 act like the older branches now do, and
requiring "-f -" only as of v13.  Yeah, the transition will be a
little slower, but this feature is not of such huge value that it
really justifies breaking scripts with zero notice.

            regards, tom lane

[1] https://www.postgresql.org/message-id/24868.1550106683%40sss.pgh.pa.us



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: v12 and pg_restore -f-
Next
From: Stephen Frost
Date:
Subject: Re: v12 and pg_restore -f-