Document that WT_SESSION::drop can return EBUSY when data is not checkpointed

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints
    • None
    • Storage Engines
    • None
    • None

      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:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: