When aborting a prepared transaction, we unconditionally run assertions that the timestamps are well ordered. Because a prepared transaction (by constraint of the API) can only have a durable timestamp assigned on the configuration string of a WT_SESSION::commit_transaction call, this assertion is doomed to fail when the update chain is otherwise timestamped.
- Assignee:
- Daniel Gottlieb (Inactive)
- Reporter:
- Daniel Gottlieb (Inactive)
- Votes:
-
0 Vote for this issue
- Watchers:
-
5 Start watching this issue
- Created:
- Updated:
- Resolved: