-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Not Applicable
-
Storage Engines
-
StorEng - Defined Pipeline
-
v8.0
We save the row key in each write operation in case the transaction will be prepared in the future. We need the saved key to look for the prepared updates if they have been evicted to disk.
However, we don't need to do that if the transaction already have a commit timestamp set as prepared transaction cannot have the commit timestamp set.
- related to
-
WT-12803 Optimise where we can skip copying keys for prepared transaction resolution
- Open