Disable triggers when performing bib visibility recalculations at the end of the 3.0.2-3.0.3 upgrade script

Bug #1758426 reported by Kathy Lussier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.1
Fix Released
Undecided
Unassigned

Bug Description

At the end of the 3.0.2-3.0.3 upgrade script, we perform a bib visibility recalculation that is similar to the one included in the 2.12.6 to 3.0.0 upgrade script. In the 2.12.6-3.0.0 script, we had disabled many triggers before performing the recalculation because they were unnecessary and took a very long time to perform.

Back in February, I asked a question in IRC about whether we should make similar changes for the new recalculation, and the answer was 'yes.' - http://irc.evergreen-ils.org/evergreen/2018-02-02#i_344301

Unfortunately, I never filed the bug. I'm doing so now.

See related list e-mail at https://georgialibraries.markmail.org/thread/gzx36cndjabhf4o4

Tags: pullrequest
Revision history for this message
Kathy Lussier (klussier) wrote :
tags: added: pullrequest
Changed in evergreen:
milestone: 3.0.6 → 3.0.7
Changed in evergreen:
milestone: 3.0.7 → 3.0.8
Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

Seemed to work fine for me, went from 3 + hours(I gave up) to 20 seconds updating 79K bib records on a slow test system with only 8GB of ram.
Josh

Revision history for this message
Ben Shum (bshum) wrote :

Fix pushed to master and backported to both rel_3_1 and rel_3_0 for more efficient upgrades.

Changed in evergreen:
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.