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

HASH_SEARCH() is duplicating effort before HASH_INSERT() or HASH_DELETE()

Details

    Description

      The InnoDB hash table implementation defines the macros HASH_SEARCH, HASH_INSERT, and HASH_DELETE. Often, a HASH_SEARCH operation would already navigate to the correct hash bucket and to the correct position for a subsequent insert or delete operation. This effort will be wasted, because there is no way for HASH_INSERT or HASH_DELETE to refer to that position.

      Similar to what was done to buf_pool.page_hash in MDEV-26826, we had better replace these macros with something more efficient, basically passing some kind of "iterator" from a search operation to the insert or delete operations.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Marko Mäkelä made transition -
            Open In Progress
            8s 1
            Marko Mäkelä made transition -
            In Progress In Review
            6d 22h 30m 1
            Marko Mäkelä made transition -
            Stalled In Review
            4d 7h 20m 1
            Debarun Banerjee made transition -
            In Review Stalled
            23d 32m 2
            Marko Mäkelä made transition -
            Stalled Closed
            19h 9m 1

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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