From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: imai.yoshikazu@fujitsu.com <imai.yoshikazu@fujitsu.com>
Cc: Euler Taveira <euler@timbira.com.br>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: v12 and pg_restore -f-
Date: Tue, 05 Nov 2019 09:28:29 -0500
Message-ID: <7897.1572964109@sss.pgh.pa.us> (raw)
In-Reply-To: <20191105141132.GK6962@tamriel.snowman.net>
References: <20191104145336.GA23924@alvherre.pgsql>
<5e124b1d-bd8f-0659-1088-4952464223bc@2ndquadrant.com>
<20191105141132.GK6962@tamriel.snowman.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, sfrost@snowman.net, peter.eisentraut@2ndquadrant.com, alvherre@2ndquadrant.com, imai.yoshikazu@fujitsu.com, euler@timbira.com.br, andrew@tao11.riddles.org.uk, pryzby@telsasoft.com, pgsql-hackers@lists.postgresql.org
Subject: Re: v12 and pg_restore -f-
In-Reply-To: <7897.1572964109@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox