From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | Scott Mead <scottm(at)openscg(dot)com> |
Cc: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Uber migrated from Postgres to MySQL |
Date: | 2016-07-27 19:33:54 |
Message-ID: | CACjxUsMxFNpPy1snp_O073TeDLzMebaZ4vWasX-6BBAaHsEnag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jul 27, 2016 at 9:22 AM, Scott Mead <scottm(at)openscg(dot)com> wrote:
> On Wed, Jul 27, 2016 at 3:34 AM, Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> wrote:
>> Our last 1TB upgrade from 9.0 -> 9.3 went like a charm in something like
>> seconds. (with the -k option)
>> However, be warned that the planing and testing took one full week.
Agreed -- you should spend a lot more time on planning and testing
than the actual upgrade will take; but that will probably be true
with any product.
> That being said, it doesn't really provide a back-out plan.
Until you get to the end of the upgrade and *start the cluster
under the new version* you can fall back to the old version. I
remember a couple times that we saw something during a pg_upgrade
--link run that we weren't expecting, and did exactly that so we
could investigate and try again later.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2016-07-27 20:06:51 | Re: Uber migrated from Postgres to MySQL |
Previous Message | Kevin Grittner | 2016-07-27 19:25:41 | Re: Uber migrated from Postgres to MySQL |