[MDEV-21895] Refactor handler::records_in_range() - Jira

XML

Word

Printable

Details

Type: New Feature
Status: Stalled (View Workflow)
Priority: Critical
Resolution: Unresolved
Fix Version/s: None
Component/s: Optimizer, Storage Engine - InnoDB
Labels:

PM Planning:

Description

According to igor, the entire function handler::records_in_range() should be replaced with something that returns the position of a key, as a floating-point number between 0 (start of index) and 1 (end of index). Perhaps we could take a collection of keys as a parameter, so that we can minimize the amount of operations on index or page latches?

Attachments

Issue Links

relates to

MDEV-19873 Different EXPLAIN SELECT DISTINCT on just created table and after deleted records

Open

MDEV-21136 InnoDB's records_in_range estimates can be way off

Closed

MDEV-19424 InnoDB's records_in_range estimates are capped at about 50%

Closed

Activity

People

Assignee:: Unassigned

Reporter:: Marko Mäkelä

Votes:: 1 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 2020-03-09 11:20

Updated:: 2025-06-11 09:22

Time Tracking

Estimated:

40d

Remaining:

30d 3h

Logged:

9d 5h

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.