Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21895

Refactor handler::records_in_range()

Details

    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

          Activity

            vlad.lesin Vladislav Lesin added a comment - - edited

            As btr_estimate_n_rows_in_range_low() was rewritten, there is nothing to do from InnoDB side until some requirements to the engine are formulated. I reassign it to igor, as he was mentioned in the description as the person who can formulate it.

            vlad.lesin Vladislav Lesin added a comment - - edited As btr_estimate_n_rows_in_range_low() was rewritten, there is nothing to do from InnoDB side until some requirements to the engine are formulated. I reassign it to igor , as he was mentioned in the description as the person who can formulate it.

            We aren't changing record_in_range() API right now. Is there anything else that needs to be done within the scope in this task inside InnoDB? Or shall it be closed?

            serg Sergei Golubchik added a comment - We aren't changing record_in_range() API right now. Is there anything else that needs to be done within the scope in this task inside InnoDB? Or shall it be closed?

            I do not see the point of closing tickets just because they are old. An API that could process several keys at once would allow more efficient traversal of the index tree, with fewer buf_pool.page_hash lookups and lock/unlock operations.

            That said, MDEV-19424 might be more important in the near future.

            marko Marko Mäkelä added a comment - I do not see the point of closing tickets just because they are old. An API that could process several keys at once would allow more efficient traversal of the index tree, with fewer buf_pool.page_hash lookups and lock/unlock operations. That said, MDEV-19424 might be more important in the near future.

            rephrased the description to be not InnoDB-specific

            serg Sergei Golubchik added a comment - rephrased the description to be not InnoDB-specific

            People

              Unassigned Unassigned
              marko Marko Mäkelä
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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