-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
-
3
-
Storage 2017-11-13, Storage 2017-12-04, Storage 2017-12-18, StorEng - Defined Pipeline
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.
- is related to
-
WT-3921 Commit timestamp should be > stable timestamp
- Closed