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

Only pass a non-NULL WT_ITEM value when allocating a WT_UPDATE with associated data

    XMLWordPrintable

Details

    • Technical Debt
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • None
    • WT10.0.0, 4.4.0-rc4, 4.7.0
    • None
    • None
    • 5
    • Storage - Tora 2020-04-20, Storage - Tora 2020-05-04

    Description

      Allocating a tombstone is currently done with the same function, __wt_update_alloc, that allocates update structures holding values. That means it is possible for callers to request a WT_UPDATE_TOMBSTONE but also pass in a non-NULL value. Indeed, that led to bugs and was fixed in WT-5745.

      Rather than fixing things up inside __wt_update_alloc, implement a better approach that means it is impossible for calling code to make this mistake.

      Attachments

        Issue Links

          Activity

            People

              keith.bostic@mongodb.com Keith Bostic
              michael.cahill@mongodb.com Michael Cahill
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: