Fix layered table key deletion and add a test for GC

XMLWordPrintableJSON

    • 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.

            Assignee:
            Chenhao Qu
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: