sql_select.cc:
if many plans have identical cost, which one will be used depends on how compiler optimizes floating-point calculations this fix adds repeatability to the optimizer sql/sql_select.cc: if many plans have identical cost, which one will be used depends on how compiler optimizes floating-point calculations this fix adds repeatability to the optimizer
This commit is contained in:
parent
df94015604
commit
851154ee30
@ -3614,7 +3614,7 @@ best_extension_by_limited_search(JOIN *join,
|
|||||||
{
|
{
|
||||||
memcpy((gptr) join->best_positions, (gptr) join->positions,
|
memcpy((gptr) join->best_positions, (gptr) join->positions,
|
||||||
sizeof(POSITION) * (idx + 1));
|
sizeof(POSITION) * (idx + 1));
|
||||||
join->best_read= current_read_time;
|
join->best_read= current_read_time - 0.001;
|
||||||
}
|
}
|
||||||
DBUG_EXECUTE("opt",
|
DBUG_EXECUTE("opt",
|
||||||
print_plan(join, current_read_time, current_record_count, idx, "full_plan"););
|
print_plan(join, current_read_time, current_record_count, idx, "full_plan"););
|
||||||
|
Loading…
x
Reference in New Issue
Block a user