-
Type: Bug
-
Resolution: Fixed
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
-
Storage - Ra 2022-02-21
-
v5.0
http://source.wiredtiger.com/develop/transactions.html#transaction_timestamps
In the above document, we said that it is not allowed to commit a transaction at the current stable timestamp.
However, in the code, it is actually allowed.
if (has_stable_ts && durable_ts < stable_ts) WT_RET_MSG(session, EINVAL, "durable timestamp %s is less than the stable timestamp %s", __wt_timestamp_to_string(durable_ts, ts_string[0]), __wt_timestamp_to_string(stable_ts, ts_string[1]));
if (has_stable_ts && commit_ts < stable_ts) WT_RET_MSG(session, EINVAL, "commit timestamp %s is less than the stable timestamp %s", __wt_timestamp_to_string(commit_ts, ts_string[0]), __wt_timestamp_to_string(stable_ts, ts_string[1]));
- depends on
-
SERVER-58410 Discontinue writing to appliedThrough/minValid as part of secondary batch application
- Closed
- is depended on by
-
SERVER-64125 MDB server sets the commit/durable timestamps equal to the stable timestamp
- Closed
- is duplicated by
-
WT-3921 Commit timestamp should be > stable timestamp
- Closed