-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
The commit/durability timestamp validation code and global set timestamp code can race, and we perform potentially unnecessary checks (since oldest is necessarily less than stable, it's unnecessary to check both).
- has to be done after
-
SERVER-65910 the server tests attempt to set illegal durable and oldest timestamps
- Closed
-
WT-8973 Define semantics of zero timestamp in our APIs
- Closed
- is duplicated by
-
WT-9174 example program ex_all not running cleanly
- Closed
- related to
-
WT-5720 Stable timestamp can be unset with an oldest timestamp set
- Closed