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

Add a test to verify checkpointing truncation in durable history

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc5, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • Storage - Ra 2020-05-18

      There is an outdate comment in bt_sync.c leading me to believe checkpointing truncation doesn't work in durable history:

      For example, if the stable timestamp at 2 and we truncate a page at timestamp 3. According to the comment, as the truncate is visible to checkpoint, checkpoint will skip the page, which should cause problems if we need to rollback the truncate in rollback to stable.

      However, I found the code is working in my test. So I checked the code and found the code doesn't work as the way described in the comment.

      Instead of ignoring the page, we write a proxy cell in the page's parent and everything works.

            Assignee:
            chenhao.qu@mongodb.com Chenhao Qu
            Reporter:
            chenhao.qu@mongodb.com Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: