[OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week to finish

[Kathy Lussier]

Hi Jesse,

After I responded to your e-mail, I submitted a bug with some code to 
make this change to the 3.0.2-3.0.3 upgrade script. If you look at the 
submitted code, you'll see exactly how you would add the lines to that 
particular script. You could copy and paste the code  the additions that 
were made to the script. If you use git, you could also cherry-pick this 
patch to apply the changes.

Please note: this patch has not been reviewed by anyone yet, so it might 
not be a bad idea for somebody to take a look at it and verify that it 
looks okay.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=blobdiff;f=Open-ILS/src/sql/Pg/version-upgrade/3.0.2-3.0.3-upgrade-db.sql;h=6ca665dad31f9e34b39b04fecc9f84ea44745ce1;hp=74a7c0117003a9db2b0d69cde85337216bdab467;hb=d1918fdd3627332a06b9d7a214544d2e46302a1a;hpb=5a6636f53ad07c718c6ba207d3f9d543deec72db

If you make those changes as is, there is a section at the end that 
reenables the triggers before it finishes up.

Kathy


On 03/29/2018 06:10 PM, Jesse McCarty wrote:
> Thanks again for the info. We are on 2.10.3 now and upgrading to 3.0.3. How would I go about re-enabling the triggers mentioned and is disabling them as simple as copy/paste the code snipped Kathy sent into the upgrade script? For combing the scripts, would it just be copy/paste the contents of each one sequentially into a single file? Do you have a workable single file upgrade script that you can share? Modifying these files is new to me.
>
> Thanks again.
>
> Jesse McCarty
> City of Burlington
> Information Systems Technician
>
> -----Original Message-----
> From: Open-ils-general [mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Jason Stephenson
> Sent: Wednesday, March 28, 2018 4:34 PM
> To: open-ils-general at list.georgialibraries.org
> Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week to finish
>
> On 03/28/2018 06:52 PM, Jesse McCarty wrote:
>> Not sure how to proceed to test getting the upgrade more manageable
>> prior to upgrading production. Obviously cannot have production down
>> or having issues for several business days.
> If you add the code to disable triggers, etc., from the 2.12.6 to 3.0 upgrade script, then it runs it much less time. It ran in about half an hour on my test system.
>
> BTW, are you upgrading from 2.10 to 3.0? If so, it sometimes helps to make a single upgrade script because some steps are occasionally repeated. In this particular case, the 2.12.6 to 3.0.0 upgrade script does this calculation. It would be wise to bundle everything up and put that update at the end so you only have to do it once, rather than twice.
>
> There's an authority ingest in that 2.12.6 to 3.0 upgrade that takes a lot longer on my test system.
>
> Jason

-- 
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
klussier at masslnc.org
Twitter: http://www.twitter.com/kmlussier