If I understand it correctly, ideally the upgrade process should look like:
9.0.x --> 9.0.23 + recommended fixes (the main is about table's relfrozenxid)
9.0.23 --> 9.4.5 (as the last version, where 9.0.23 was supported)
9.4.5 --> 9.4.10 + fixes
9.4.10 --> 9.6.1
Wednesday, December 14, 2016 12:55 PM +03:00 from Thomas Kellerer <spam_eater@xxxxxxx>:
Mikhail schrieb am 13.12.2016 um 10:57:
> 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?
There is a nice page which consolidates all release notes:
https://bucardo.org/postgres_all_versions.html
The nice thing about that is, that for each change in one release, it also mentions if that was a change in other releases too, e.g.:
https://bucardo.org/postgres_all_versions.html#version_9.6.1
Thomas
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
