pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
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, 5 Nov 2019 09:11:32 -0500
Message-ID: <20191105141132.GK6962@tamriel.snowman.net> (raw)
In-Reply-To: <5e124b1d-bd8f-0659-1088-4952464223bc@2ndquadrant.com>
References: <20191104145336.GA23924@alvherre.pgsql>
	<5e124b1d-bd8f-0659-1088-4952464223bc@2ndquadrant.com>

Greetings,

* 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.
> 
> Users with with hundreds or thousands of servers and various ancient
> maintenance scripts lying around in hard-to-track ways are not going be able
> to get everything upgraded to the latest minors *and* new script versions
> any time soon.  Until they do, they are effectively blocked from introducing
> PG12 into their environment.  This is very complicated and risky for them.
> 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.

We don't guarantee this kind of compatibility between major versions.
Those users have years to address these kinds of changes, that's why we
have back-branches and support major versions for 5 years.

Thanks,

Stephen

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (38+ messages)  latest in thread

Message-ID: <20191105141132.GK6962@tamriel.snowman.net>
Permalink:  ../20191105141132.GK6962@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20191105141132.GK6962@tamriel.snowman.net

 · 

reply

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: sfrost@snowman.net, peter.eisentraut@2ndquadrant.com, alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, 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: <20191105141132.GK6962@tamriel.snowman.net>

* 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