Bug #23769 | Debug assertion failure with innodb_locks_unsafe_for_binlog | ||
---|---|---|---|
Submitted: | 30 Oct 2006 12:05 | Modified: | 27 Nov 2006 19:10 |
Reporter: | Heikki Tuuri | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0 | OS: | Any (All) |
Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
Tags: | innodb_locks_unsafe_for_binlog |
[30 Oct 2006 12:05]
Heikki Tuuri
[31 Oct 2006 12:43]
Heikki Tuuri
Marko has an approved patch for 5.0 (the patch is backported from 5.1).
[15 Nov 2006 9:46]
Marko Mäkelä
Proposed changelog entry: The internal SQL interpreter of InnoDB placed an unnecessary lock on the supremum record when innodb_locks_unsafe_for_binlog=1. This caused an assertion failure when InnoDB was built with debugging enabled.
[27 Nov 2006 19:10]
Paul DuBois
Thanks, Marko. Noted in 5.0.30 (not 5.0.29) changelog.