-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Reconciliation
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-09-12
-
3
We garbage collect the ingest table through reconciliation done by evictions. It will remove any update that has been included in the stable table. However, tombstone is a special case and we are handling it incorrectly.
Suppose a tombstone is globally visible but it is not included in the stable table yet, currently reconciliation still removes it from the ingest table. This leads to the key wrongly reappear in layered cursor search. This is a temporary visibility failure and will be fixed when we adopt a new checkpoint that removes the key.
- related to
-
WT-14904 Add more scenarios for the internal page deltas
-
- Closed
-
-
WT-15213 Don't free the previous address cookie
-
- Closed
-
-
WT-15233 Fix behavior of dmalloc, dcalloc, drealloc used in testing to match malloc, etc.
-
- Closed
-
-
WT-15247 Unexpected keys observed after connection reopen for disagg
-
- Closed
-
-
WT-15249 Add error check for incompatible config with write_timestamp_usage=never in disagg
-
- Closed
-
-
WT-15396 Coverity analysis defect 175990: Calling risky function
-
- Closed
-
-
WT-15187 Don't build overflow keys or values in disagg
-
- Closed
-
-
WT-15401 Make test/model compatible with macOS
-
- Closed
-
-
WT-15389 Saved update lists with deletes are lost when building a delta
-
- Closed
-