Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 10.0
-
Fix Version/s: 10.0
-
Component/s: None
-
Labels:None
Description
In sql/sql_class.cc, THD::cleanup() calls apc_target.destroy().
The latter has:
DBUG_ASSERT(!enabled) which fails during our test which triggers this code path.
The fix is to disable apc_target if it is enabled before destroying it.
Proposed patch:
void THD::cleanup(void)
{
...
DBUG_ASSERT(!mdl_context.has_locks());
+ if (apc_target.is_enabled())
+ apc_target.disable();
apc_target.destroy();
...
}
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Can you show your tests or explain how to trigger that?
As far as I can see apt_target should be disabled when lex->explain is destroyed.
Does it only happen in the context of MDEV-7095 — when you invoke that dead code in Ed_connection::execute_direct() ?