Consider documenting 'checkpoint_wait', 'lock_wait', and EBUSY for uncheckpointed tables in WT_SESSION::drop

XMLWordPrintableJSON

    • Type: Documentation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: APIs, WT Docs
    • Storage Engines, Storage Engines - Foundations
    • StorEng - Defined Pipeline, StorEng - 2024-10-01, StorEng - 2024-10-15, StorEng - 2024-10-29, StorEng - 2024-11-12
    • 3

      The docs for WT_SESSION::drop state "This method requires exclusive access to the specified data source(s). If any cursors are open with the specified name(s) or a data source is otherwise in use, the call will fail and return EBUSY"

      But it does not mention that EBUSY is also returned if the table has not yet been checkpointed.

      The docs also don't mention the undocumented parameters "checkpoint_wait" and "lock_wait".

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: