Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
N/A
-
None
Description
I thought that improvements to JSON writer would make this impossible, but
somehow they didn't?
create table ten(a int); |
insert into ten values (0),(1),(2),(3),(4),(5),(6),(7),(8),(9); |
set optimizer_trace=1; |
select * from ten where a<3 ; |
produces:
"steps": [
|
{
|
...
|
},
|
...
|
{
|
"ref_optimizer_key_uses": []
|
},
|
"rows_estimation": [
|
{
|
"selectivity_for_indexes": [],
|
"selectivity_for_columns": []
|
},
|
{
|
"table": "ten",
|
"table_scan": {
|
"rows": 10,
|
"cost": 1
|
}
|
}
|
],
|
Note that "rows_estimation" is a named element, but it is in the "steps" array.
Attachments
Issue Links
- is part of
-
MDEV-6111 optimizer trace
-
- Closed
-
execution_plan_for_potential_materialization has the same problem.