Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5134

Fix leaf-page only search and search-near operations

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1, WT10.0.0, 4.2.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage Engines 2019-10-07

      WT-3769 broke leaf-page only searches.

      The WT_CURSOR.search and WT_CURSOR.search_near operations are supposed to search any pinned Btree leaf page (that is, any page pinned as a result of a previous operation), assuming locality of reference, that a search is likely to hit on the currently pinned page. Commit 00e1b59 broke this by checking if the current key was internal (referencing an on-page key) or external (referencing a key set by the application using WT_CURSOR.set_key). That test was correct for non-search operations (for example, WT_CURSOR.update, but not for search operations).

            keith.bostic@mongodb.com Keith Bostic (Inactive)
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            0 Vote for this issue
            3 Start watching this issue