If two tables exist with each referring to the other, executing an update on either of the tables causes MariaDB to get stuck indefinitely, using 100% of CPU.
This seems to be affecting all 10.x releases so far, but this is the first time I have had a test case this small and compact to reproduce it. The same issue does not arise on MySQL 5.1, so this is a regression (and quite a nasty one).
Attached is a data set with which the problem is reproducible, just two tables with three records between them.
cat the attached file into an empty database, and execute the following query on it:
The query will go away forever with the mysqld thread executing it consuming 100% CPU until killed (can only be killed with kill -9).