Hi, Galen!
Thanks for sharing your answer.
On 7/21/21 1:52 PM, Galen Charlton wrote:
I suggest running with whatever is current on the master branch at the
time you generate the database, but at the moment there isn't much of a
difference that should affect performance between 3.7.1 and the tip of
master.
It looks like there are 6 database updates in master (d9bb7c9205) since
3.7.1.
I made 3 upgrade scripts:
1. 3.5.3 to 3.7.1
2. 3.5.3 to master@d9bb7c9205
3. 3.7.1 to master@d9bb7c9205
At the moment, I think I should start over, and load the database once,
upgrade it to master, do the did you mean steps, dump it, and then load
that dump. This might save some time over going through the upgrade
steps on each instance. However, doing the upgrade on each instance
might uncover something where the upgrade fails on a particular Pg release.
I wonder if I should make a Lp bug if I haven't already, or set up a
shared document somewhere to track progress and get suggestions of what
to look at?
Jason
_______________________________________________
Evergreen-dev mailing list
Evergreen-dev@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
