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

No need to save the row key if the we already have a commit timestamp set

    • Storage Engines
    • StorEng - Defined Pipeline
    • v8.0

      We save the row key in each write operation in case the transaction will be prepared in the future. We need the saved key to look for the prepared updates if they have been evicted to disk.

      However, we don't need to do that if the transaction already have a commit timestamp set as prepared transaction cannot have the commit timestamp set.

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

              Created:
              Updated:
              Resolved: