-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
The stable timestamp in test/format is set to the current timestamp, it really should lag the current timestamp, and ahead of the oldest timestamp.
Also there's no reason that the stable timestamp shouldn't move unconditionally (currently it only moves if return_to_stable is enabled).
- is duplicated by
-
WT-6423 Salvage testing fails after setting stable timestamp in test format
- Closed