https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26457 --- Comment #4 from David Cook <dcook@prosentient.com.au> --- (In reply to didier from comment #3)
It's also our analysis, there's redundant indexes on issues which may on may not compound the problem. PRIMARY KEY (`issue_id`), UNIQUE KEY `itemnumber` (`itemnumber`), KEY `issuesborridx` (`borrowernumber`), KEY `itemnumber_idx` (`itemnumber`), KEY `branchcode_idx` (`branchcode`), KEY `bordate` (`borrowernumber`,`timestamp`),
itemnumber_idx and issuesborridx are redundant.
I doubt that the indexes compound the problem, but I suppose more investigation would be needed. I see that itemnumber_idx is redundant, but how is issuesborridx redundant? It's not the same as bordate.
I'll try, maybe adding a fat sleep(5) in transaction block.
Certainly worth experimenting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.