Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.16, 10.0(EOL)
Description
Hi,
FYI, the latest TokuDB version included in MariaDB 10.1.16 contains a nasty bug which could lead to cardinality wrongly set to 0 for all the keys (with the impact on the execution plan you can imagine).
Detail of the bug (now fixed) upstream is here :
https://tokutek.atlassian.net/browse/DB-1006
Since it could lead to really bad issues, I wonder if you want to cherry pick the bugfix to include it in MariaDB, or just wait for the next TokuDB engine 5.6.32-77.1 release.
Thanks,
Jocelyn