revno: 4334.1.2
committer: Jon Olav Hauglid <email address hidden>
branch nick: mysql-5.5.32-release
timestamp: Mon 2013-05-06 16:06:32 +0200
message: Bug#16757869: INNODB: POSSIBLE REGRESSION IN 5.5.31, BUG#16004999
The problem was that if UPDATE with subselect caused a
deadlock inside InnoDB, this deadlock was not properly
handled by the SQL layer. This meant that the SQL layer
would try to unlock the row after InnoDB had rolled
back the transaction. This caused an assertion inside
InnoDB.
This patch fixes the problem by checking for errors
reported by SQL_SELECT::skip_record() and not calling
unlock_row() if any errors have been reported.
This bug is similar to Bug#13586591, but for UPDATE
rather than DELETE. Similar issues in filesort/opt_range/
sql_select will be investigated and handled in the scope
of Bug#16767929
=====================================
Looks like filesort is still not fixed (in 5.5.32, need to test with 5.5.33), and Bug#16767929 is still not in log.
Related Commit info:
revno: 4334.1.2 5.32-release
Bug#16757869: INNODB: POSSIBLE REGRESSION IN 5.5.31, BUG#16004999
committer: Jon Olav Hauglid <email address hidden>
branch nick: mysql-5.
timestamp: Mon 2013-05-06 16:06:32 +0200
message:
The problem was that if UPDATE with subselect caused a
deadlock inside InnoDB, this deadlock was not properly
handled by the SQL layer. This meant that the SQL layer
would try to unlock the row after InnoDB had rolled
back the transaction. This caused an assertion inside
InnoDB.
This patch fixes the problem by checking for errors :skip_record( ) and not calling
reported by SQL_SELECT:
unlock_row() if any errors have been reported.
This bug is similar to Bug#13586591, but for UPDATE ======= ======= ======= ======= ==
rather than DELETE. Similar issues in filesort/opt_range/
sql_select will be investigated and handled in the scope
of Bug#16767929
=======
Looks like filesort is still not fixed (in 5.5.32, need to test with 5.5.33), and Bug#16767929 is still not in log.