-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Layered Tables, Verify
-
None
-
Storage Engines - Persistence
-
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