| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh berkus <josh(at)agliodbs(dot)com>, Justin Clift <justin(at)postgresql(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0 |
| Date: | 2016-05-20 23:40:53 |
| Message-ID: | CA+TgmoZXhkxNRits8enFWsXEK_O7szHcj_6yvNTB8SFcXk-gMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 16, 2016 at 3:36 AM, Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-20 23:47:53 | Re: what to revert |
| Previous Message | Robert Haas | 2016-05-20 23:37:49 | Re: Parallel safety tagging of extension functions |