Bug #71962 | Optimizer prefers table scan when using "in" with value of different type | ||
---|---|---|---|
Submitted: | 7 Mar 2014 2:40 | Modified: | 31 Mar 2014 16:26 |
Reporter: | NOT_FOUND NOT_FOUND | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.6.16 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[7 Mar 2014 2:40]
NOT_FOUND NOT_FOUND
[7 Mar 2014 8:08]
MySQL Verification Team
Hello!! Thank you for the bug report. Verified as described. Thanks, Umesh
[31 Mar 2014 16:26]
Paul DuBois
Noted in 5.7.5 changelog. For IN() predicates with values different from the key data value, the optimizer sometimes used a table scan when it could do a range scan.