-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Layered Tables, Verify
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines - Persistence
-
1,305.313
-
SE Persistence backlog
-
None
See WT-15476 for motivations.
Here is what needs to be done:
- Only check the most up-to-date update about to be pruned (not all updates in the chain)
- If that last update is a tombstone → the key must not exist in the stable table
- If it's a data value → it must exist and match in the stable table
- Diagnostic mode only
- has to be done before
-
WT-17190 During GC, verify older updates against the HS
-
- Open
-
-
WT-17192 During GC, verify the most recent update against the stable table in release build
-
- Open
-
- is related to
-
WT-15633 Combine btree->ckpt_timestamp and btree->prune_timestamp into one variable or a union
-
- Open
-
- related to
-
WT-17554 Fix WT_UPDATE_PREPARE_ROLLBACK regression in GC obsolete check allowing live tombstones to be freed
-
- Closed
-