-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
Heiko Braun will the postgres upgrade be handled as part of the upgrade process for 7.6? I don't know if we have an issue for that and we should not forget about it.
There are two important things to keep in mind:
1. someone who installed 7.5.0 from scratch (thus using 9.6 postgres) should not upgrade to 7.5.1 (that will bring postgres 9.5 back and he will be in the exact same situation) - his installation will therefore use 9.6 postgres
2. someone who is upgrading from older versions should skip 7.5.0 (9.5 vs 9.6 postgres) and should upgrade to 7.5.1 instead (so that it will still use the 9.5 postgres) - his installation will use 9.5 postgres.
Now when they will want to upgrade to 7.6, it looks like we will need to handle both scenarios.\
Problem Matrix: https://docs.google.com/document/d/1bSJLvTHiJL5dyC86sJ6FGizu9qWXwaYj1fuSD8-YpFs/edit?usp=sharing
- is related to
-
ENTESB-13073 Upgrade tries to upgrade postgres even if the version is the same
- Done
-
ENTESB-13074 Upgrade db fails with sampledb integration active
- Done
- relates to
-
ENTESB-12328 Postgres upgrade from 9.5 to 9.6 won't use the old data dir
- Done
-
ENTESB-12359 Fuse Online 7.5.1
- Closed
1.
|
Add upgrade steps that can perform the Postgres dataDir conversion if needed | Closed | Unassigned | ||
2.
|
Verify the upgrade from 7.5.1 to 7.6 | Closed | Andrej Vano | ||
3.
|
Verify the upgrade from 7.5 to 7.6 | Closed | Andrej Vano |