-
Type:
Task
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Concurrency
-
None
-
Storage Engines - Foundations
-
806.123
-
None
-
None
Currently, we have a macro WT_SINGLE_THREAD_CHECK_START that checks that a session can be used by only one thread at a time.
However, it does not produce a very informative message in case of an assertion failure. When we get a BF caused by this assertion, it is hard to understand the root cause of the issue.
The main purpose of this ticket is to improve logging in case of failure.