-
Type:
Technical Debt
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Schema Management
-
Storage Engines, Storage Engines - Foundations
-
StorEng - Defined Pipeline
-
5
__drop_table currently contains the following comment
/*
* Open the table so we can drop its column groups and indexes.
*
* Ideally we would keep the table locked exclusive across the drop, but for now we rely on the
* global table lock to prevent the table being reopened while it is being dropped. One issue is
* that the WT_WITHOUT_LOCKS macro can drop and reacquire the global table lock, avoiding
* deadlocks while waiting for LSM operation to quiesce.
*
* Temporarily getting the table exclusively serves the purpose of ensuring that cursors on the
* table that are already open must at least be closed before this call proceeds.
*/
The comment first appeared here.
We should revisit this and determine whether the global table lock is still necessary over the handle exclusive lock.
- is related to
-
WT-12751 LSM: remove feature
-
- Closed
-