Build with UNIV_DEBUG causes asserts
Bug #418838 reported by
Seppo Jaakola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
Low
|
Seppo Jaakola |
Bug Description
It turns out that build with UNIV_DEBUG defined, causes assert(s).
At least in loc0lock.
ut_ad((type_mode & (LOCK_WAIT | LOCK_GAP))
|| ((type_mode & LOCK_MODE_MASK) != LOCK_X)
|| !lock_rec_
rec, trx));
,where lock_rec_
Changed in codership-mysql: | |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
importance: | Undecided → Low |
milestone: | none → 0.7 |
status: | New → In Progress |
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
wsrep code path does not cancel the waiting, if victim is in waiting state.
This is because we want to control that victim does no leave, before we put our lock in the lock queue.
This change in locking protocol caused the assert to fail.