Handle prepared updates when walking the stable table on standby

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Btree, Cursors
    • None
    • Storage Engines, Storage Engines - Transactions
    • SE Transactions - 2025-10-10
    • 5

      When seeing a prepared update on the stable table on standby, we need to decide whether we should block the read by throwing a prepared conflict or continue the walk. This is important for the search near logic and cursor read and next walks for the layered tables.

      If we have seen the prepared from the same key on the ingest table, we should ignore the prepared update on the stable table. Otherwise, we should block the walk by throwing a prepared conflict.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: