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

Add a diagnostic check for updates to the same key out of timestamp order

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.3, 3.7.2, WT3.1.0
    • Component/s: None
    • Labels:
      None

      Description

      The documentation in docs/transactions.dox states:

      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.
      

      I attach a simple python unit test that illustrates this is not being checked in a diagnostic build.

      The code should be brought in line with the documentation.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sue.loverso Susan LoVerso
                Reporter:
                sue.loverso Susan LoVerso
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: