Verify discards all data for published but uncheckpointed tables

XMLWordPrintableJSON

    • Storage Engines - Foundations
    • 218.439
    • None
    • None

      Verify closes the live handle so that it can open an exclusive dhandle, which results in any data for an AWAITS_PUBLISH table being discarded. This should instead return EBUSY.

      Claude tells me that the same thing can happen via handle sweeping. I am unsure if that is actually true or if the timing required for handle sweeping to close the handle for a published but uncheckpointed table is reasonably possible. The P2 priority is assuming that it can; if this is actually specific to verify then this is a P3.

      The attached test case reproduces this with verify.

            Assignee:
            Jie Chen
            Reporter:
            Thomas Goyne
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: