Since few days I was debugging a case from Yahoo! Japan team (thanks to Akira Kitada) where the query runs fine in about 0 secs with the 5.1.16 build where as the same query takes almost close to 2 minutes with the latest 5.1.22 release.
One can simply identify that this is a optimizer issue as it is not picking the right index. Lets consider the following two tables urls and urls_categories…
| [Copy to clipboard][-]View Code | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
| urls | CREATE TABLE `urls` ( `url_id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT, `url` VARBINARY(2000) NOT NULL, `url_status` … |