From: | Mikhail <bemewe(at)mail(dot)ru> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re[2]: [GENERAL] pg_upgrade 9.0 to 9.6 |
Date: | 2016-12-14 09:47:33 |
Message-ID: | 1481708853.546438528@f434.i.mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
John, thanks! Your approach significantly reduces the number of checks.
>Вторник, 13 декабря 2016, 13:34 +03:00 от John R Pierce <pierce(at)hogranch(dot)com>:
>
>On 12/13/2016 1:57 AM, Mikhail wrote:
>> Should i check all the production environments for the problems,
>> mentioned in all interim versions release notes, is it enough only to
>> check the last minor upgrade release note (9.6 --> 9.6.1) or there is
>> another quick way to check if i should apply some additional actions
>> to standard pg_upgrade+stats_collect?
>
>if you're upgrading directly from 9.0.x to 9.6.1, I would only check the
>release notes for 9.0.latest (and upgrade to that, following those notes
>and any 9.0.x release newer than your current which are referenced in
>hte 9.0.latest notes), then do the pg_upgrade directly to 9.6.1
>
>now, there could be application compatibility issues going from 9.0 to
>9.6, those would best be addressed by 9.1.0, 9.2.0, ... release notes as
>9.6 will include all those functional changes.
>
>
>--
>john r pierce, recycling bits in santa cruz
>
>
>
>--
>Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2016-12-14 09:55:36 | Re: pg_upgrade 9.0 to 9.6 |
Previous Message | Torsten Förtsch | 2016-12-14 09:12:23 | Re: vacuum freeze in 96 |