For those who saw my previous post about the crashing (regression) bug with SELECT COUNT(DISTINCT) on InnoDB with Primary Key (PK), you’ll be interested to know my test case does not crash in 5.5.18 (which was just released).
I’ve only tested my test case thus far, but it seems fine.
Unfortunately, the fix is not mentioned in the 5.5.18 changelogs though.
And there is no mention (yet, anyway) of a fix in the bug report I filed (though it was designated a ‘duplicate’, so it wouldn’t necessarily be updated).
I’m trying to get confirmation from the MySQL Dev Team on this (via the bug report), and will update this post if/when I hear anything.
I’ll also perform some of the other tests on my end to see if they all pass as well.
All in all, at least the initial results look very promising!
Tags: 5.5, 5.5.18, btr_pcur_restore_position_func, bug, crash, ha_innobase, index_next_different, MySQL, os0sync.c, QUICK_GROUP_MIN_MAX_SELECT, regression, regression bug fixed, row_search_for_mysql, SELECT COUNT(DISTINCT), sel_restore_position_for_mysql