When there are multiple updates from the same transaction including a delete operation and if that transaction gets prepared while reconciling the page as part of eviction, the earlier updates before tombstone must be squashed to point the tombstone to the earlier update. If there are no tombstones associated with the prepared transaction, the squashing is already taken care during the insertion of these updates into the history store.
- causes
-
WT-6679 Shouldn't squash updates from the same transaction but with different timestamps onto data store
- Closed