Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0
Date
Msg-id CA+TgmoZXhkxNRits8enFWsXEK_O7szHcj_6yvNTB8SFcXk-gMQ@mail.gmail.com
Whole thread Raw
In response to Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Mon, May 16, 2016 at 3:36 AM, Bruce Momjian <bruce@momjian.us> wrote:
> On Sun, May 15, 2016 at 03:23:52PM -0500, Jim Nasby wrote:
>> 2) There's no ability at all to revert, other than restore a backup. That
>> means if you pull the trigger and discover some major performance problem,
>> you have no choice but to deal with it (you can't switch back to the old
>> version without losing data).
>
> In --link mode only

No, not really.  Once you let write transactions into the new cluster,
there's no way to get back to the old server version no matter which
option you used.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel safety tagging of extension functions
Next
From: Robert Haas
Date:
Subject: Re: what to revert