Issue Bug Closed

#88487Upgrade step SeparateSysHistoryFromSysLogUpdate has problems with large amounts of data

Stefan Berger 06/04/19, 15:02 updated 04/01/20, 21:14

Description

Hi,

in some cases when the sys_history or sys_log tables contain large amounts of data, in our case about 600 MB and 250 MB, the SeparateSysHistoryFromSysLogUpdate update step silently exits.

Deeper debuggings lead us to the point in \Doctrine\DBAL\Driver\Mysqli\MysqliStatement::execute, where will be called the $this->_stmt->store_result(); method.

So our fix to handle this is to do the jobs in smaller blocks. @see attached patch file.

Thanks for fixing.

Reviews 2