innodb: unprotected access to was_chosen_as_deadlock_victim
Bug #1233383 reported by
Teemu Ollakka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
Critical
|
Seppo Jaakola | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Innodb trx->lock.
Changed in codership-mysql: | |
milestone: | none → 5.6.14-24.1 |
assignee: | nobody → Teemu Ollakka (teemu-ollakka) |
importance: | Undecided → Critical |
Changed in codership-mysql: | |
assignee: | Teemu Ollakka (teemu-ollakka) → Seppo Jaakola (seppo-jaakola) |
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
a potential fix pushed in here: http:// bazaar. launchpad. net/~codership/ codership- mysql/5. 6/revision/ 3953
tested with 2 node cluster, seriously conflicting sqlgen load through glb