Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Won't Do
-
None
-
None
-
None
-
Storage Execution
-
ALL
Description
One assumption for the RAII database lock types was that destruction order is always the reverse of construction order. However, with increasing usage of unique_ptr and boost::optional for more dynamic locking, we need additional checking that locking semantics are not violated.
Attachments
Issue Links
- related to
-
SERVER-30371 Separate renameCollection across DB commands into individual oplog entries
-
- Closed
-