-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
If you commit twice to the same key such that the commit timestamps are in order, but the durable timestamps are reversed, we assert in reconciliation when moving the first value to history.
Since we think out of order commits are going away entirely, with luck this is a nonissue.
However, the in-order timestamp assertions probably ought to be checking up front that durable timestamps on individual items don't go backwards; evidently that's not currently the case.
Will attach a simple reproducer.
- is depended on by
-
SERVER-64131 Turn on WT write_timestamp_usage assertions for release builds
- Closed
- is duplicated by
-
WT-8887 Overlapping delayed-durable commits generate corrupted database pages
- Closed
- related to
-
SERVER-76747 Remove use of deprecated WT config assert(write_timestamp)
- Closed