[MDEV-33054] ANALYZE FORMAT=JSON: rowid_filter.r_lookups should be average, not total Created: 2023-12-18 Updated: 2024-01-04 |
|
| Status: | In Progress |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 10.6 |
| Fix Version/s: | 10.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Sergei Petrunia | Assignee: | Sergei Petrunia |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | analyze-stmt, rowid_filtering | ||
| Issue Links: |
|
||||||||
| Description |
|
Consider this example from mysql-test/main/rowid_filter.result:
.
There are r_loops=71 lookups made for table lineitem. However, the average per-scan number of rowid_filter.r_lookups would have been more useful. r_lookups=476 is not directly comparable to anything. The per-scan average of 476/71= 6.7 rows is comparable: we see the estimate table.rows=4. We've got 6.7 on average and rowid filter has reduced it to 0.154929577. This MDEV is about making rowid_filter.r_lookups to be per-scan average. |