-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
6
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
When writing to config.transaction documents, we make an optimization to only write the latest value. This can happen for vectored inserts on a primary or after an batch of oplog application. However, after rolling back, we're expected to have the appropriate version of config.transactions documents as of the stable timestamp. Because the storage engine may never have been told about the document, we fix this by synthesizing the right version and persisting it without a timestamp. That update violates the ordered constraint.
- depends on
-
WT-9201 change mixed-mode to a per-transaction basis
-
- Closed
-
- has to be done before
-
WT-9276
remove support for mixed-mode
-
- Closed
-
- is duplicated by
-
SERVER-66253 Remove cases of write_timestamp_usage=mixed_mode
-
- Closed
-
- related to
-
-
- Closed
-