Bug #59843 | using uninitialised value in uses_index_fields_only | ||
---|---|---|---|
Submitted: | 31 Jan 2011 13:26 | Modified: | 7 Dec 2011 3:17 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | mysql-trunk | OS: | Any |
Assigned to: | Tor Didriksen | CPU Architecture: | Any |
Tags: | index_condition_pushdown, optimizer_switch, regression, valgrind |
[31 Jan 2011 13:26]
Shane Bester
[31 Jan 2011 13:27]
MySQL Verification Team
some infos
Attachment: bug59843_info.txt (text/plain), 7.95 KiB.
[1 Feb 2011 9:22]
Valeriy Kravchuk
I can confirm that this is not repeatable with valgrind build of current mysql-5.1 tree on 32-but Ubuntu 10.04.
[1 Feb 2011 13:25]
Valeriy Kravchuk
Actually, uses_index_fields_only() is a new function in mysql-trunk. Not present even in 5.5. Verified by code review.
[1 Feb 2011 13:54]
Olav Sandstå
This valgrind error is in the code for Index Condition Pushdown (which is new code for 5.6). The error goes away if disabling index condition pushdown by adding the following to the test case: set optimizer_switch='index_condition_pushdown=off';
[7 Dec 2011 3:17]
Paul DuBois
Noted in 5.6.3 changelog. Index condition pushdown code accessed an uninitialized variable.