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

History store isn't visible to wt dump

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.5.1, 4.4.0-rc7
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Sprint:
      Storage - Ra 2020-06-01

      Description

      When we moved WT_CURSTD_IGNORE_TOMBSTONE from being a session flag to a cursor flag, we broke wt dump. wt dump uses a dump cursor which delegates calls to the cursor API to a "child" cursor. We need to set the flag on the child cursor for this to work.

      We also modified the check in __wt_txn_read such that we will read the on-disk value's stop time pair even with WT_CURSTD_IGNORE_TOMBSTONE enabled if it is globally visible. This isn't useful for wt dump so we need an exception here.

        Attachments

          Activity

            People

            Assignee:
            alex.cameron Alex Cameron
            Reporter:
            alex.cameron Alex Cameron
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: