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

Fix leak of updates from history store

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT10.0.0, 4.4.0-rc0, 4.7.0
    • Component/s: None
    • Labels:
      None

      Description

      What I’m seeing is that the code to do unconditional removes from history store installs a tombstone update over the top of any existing updates — i.e., it creates an update chain with the tombstone but doesn’t link it to any existing updates already in the tree, so they become unreachable.

      __wt_row_modify just swaps its update argument into place. Callers are responsible for pointing to the existing updates in the list. This shouldn’t be an issue for the original inserts into history because we expect them to be new. It would be good to check that, of course.

        Attachments

          Activity

            People

            Assignee:
            michael.cahill Michael Cahill
            Reporter:
            michael.cahill Michael Cahill
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: