InnoDB lock monitor output is printed even if not requested
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
5.5 |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
lock_print_
{
...
loop:
/* print transaction info */
...
if (!srv_print_
nth_trx++;
goto loop;
}
/* print lock info */
goto loop;
}
The above code means that the lock info is printed if either innodb lock monitor is on, either innodb_
This shows up as innodb-status-ouput --big-test test failure on 5.6:
innodb.
Test ended at 2015-02-06 11:16:44
CURRENT_TEST: innodb.
# ERROR: The file '/Users/
->
...
Related branches
- Laurynas Biveinis (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedstorage/innobase/lock/lock0lock.c (+1/-1)
- Laurynas Biveinis (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedstorage/innobase/lock/lock0lock.cc (+1/-1)
tags: | added: ci xtradb |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PS-1609