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

Missing checks on commit_timestamp

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2017-11-13, Storage 2017-12-04, Storage 2017-12-18

      Description

      Transactions document says:

      1. Commit timestamps cannot be set in the past of any read timestamp that has been used. This is enforced by assertions in diagnostic builds, if applications violate this rule, data consistency can be violated.

      2. The commits to a particular data item must be performed in timestamp order. Again, this is only checked in diagnostic builds and if applications violate this rule, data consistency can be violated.

      Though documented I couldn't find these checks/asserts in the code.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-storage-engines Backlog - Storage Engines Team
            Reporter:
            sulabh.mahajan Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: