Issue 1871: Schema upgrade process should use transactions
Status:  New
Owner: ----
Reported by pedah...@gmail.com, Apr 17, 2013
While upgrading from 2.1.8 to 2.5.2, I noticed a couple schema upgrade steps, particularly 58 to 59 and 59 to 60 took very little CPU in MySQL, but caused ~97% I/O wait.  Looking at the process list seemed to show a lot of update statements.

Not looking at the code, I'm going to guess that these update statements are not put inside a transaction.  The Schema upgrade process would got *much* faster if all the update statements were put inside a single transaction.