-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Diagnostics, Querying, Storage
-
Fully Compatible
-
Query F (02/01/16)
The "profile" command allows the user to either read or write the profiling level for the given database.
Currently, this command always takes an exclusive lock on the given database. Instead, the command should take a shared lock on the database if the user request is to simply read the database's current profiling level.
- related to
-
SERVER-55034 The profile command should not take S or X database locks
- Closed