Hi all,
We've tested upgrading from postgresql 9.0.x to 9.6.1 on the test environment and everything passed fluently. But there are concerns about the production environments upgrade because of notes to some interim updates that recommends reindex and/or vacuuming to exclude data corruption, index results and etc.
Some examples:
9.6.0 to 9.6.1
https://www.postgresql.org/docs/9.6/static/release-9-6-1.html
if your installation has been affected by the bugs described in the first two changelog entries below, then after updating you may need to take action to repair corrupted free space maps and/or visibility maps.
9.5.1 to 9.5.2
https://www.postgresql.org/docs/9.6/static/release-9-5-2.html you may need to REINDEX some indexes after applying the update, as per the first changelog entry below
9.4.5 to 9.4.6
https://www.postgresql.org/docs/9.6/static/release-9-4-6.html if you are upgrading an installation that contains any GIN indexes that use the (non-default) jsonb_path_ops operator class, see the first changelog entry below.
9.4.1 to 9.4.2
https://www.postgresql.org/docs/9.6/static/release-9-4-2.html if you use contrib/citext's regexp_matches() functions, see the changelog entry below about that
9.3.4 to 9.3.5
https://www.postgresql.org/docs/9.6/static/release-9-3-5.html this release corrects a logic error in pg_upgrade, as well as an index corruption problem in some GiST indexes. See the first two changelog entries below to find out whether your installation has been affected and what steps you should take if so
... and so on.
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?
Regards, Mikhail Balayan