-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
We already forbid user to set a read timestamp if not running in snapshot isolation. However, we don't restrict them to commit with a timestamp. If user does that, it can lead to out of order timestamp commits. As a part of the change to solve WT-5869, we should forbid committing with timestamps if not running in snapshot.
- split from
-
WT-5869 We can't ignore updates with out of order timestamps when inserting them into the history store
- Closed