-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: History Store, Truncate
-
Storage Engines
-
22,043.806
-
2024-04-02 - GreatMugshot, 나비 (nabi) - 2024-04-16
-
8
Currently, we don't do any cleanup of the history store for any pages being fast truncated. This creates a problem if we fast truncate the page without a timestamp.
Suppose the page has a key with timestamp 50, and a history store record with timestamp 30 and we fast truncate the key. Then we reinsert the same key with timestamp 60. The value with timestamp 30 in the history store now comes back to life again.
- is related to
-
-
- Closed
-
-
WT-10949 Allow truncate operation with no timestamp for non standalone builds
-
- Closed
-
- related to
-
-
- Needs Scheduling
-
-
WT-18551 Altering write_timestamp_usage to never bypasses the fast-truncate history-store guard from WT-10013
-
- Closed
-
-
-
- Closed
-