Oracle 5.0 Reference Manual page 1264

The crash recovery mode. Possible values are from 0 to 6. The meanings of these values are
described in Section 14.2.5.2, "Forcing
Warning
This variable should be set greater than 0 only in an emergency situation
when you want to dump your tables from a corrupt database! As a safety
measure,
greater than 0.
•
innodb_lock_wait_timeout
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
The timeout in seconds an
value is 50 seconds. A transaction that tries to access a row that is locked by another
transaction will hang for at most this many seconds before issuing the following error:
ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
When a lock wait timeout occurs, the current statement is not executed. The current transaction
is not rolled back. (Until MySQL 5.0.13
wait timeout happened. You can restore this behavior by starting the server with the
innodb_rollback_on_timeout
Section 14.2.11, "InnoDB
innodb_lock_wait_timeout
not happen inside
InnoDB
does detect transaction deadlocks in its own lock table immediately and rolls back one
InnoDB
transaction. The lock wait timeout value does not apply to such a wait.
•
innodb_locks_unsafe_for_binlog
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Deprecated
Startup Options and System Variables
InnoDB
6
InnoDB
prevents any changes to its data when this variable is
InnoDB
--innodb_lock_wait_timeout=#
innodb_lock_wait_timeout
Yes,
innodb_lock_wait_timeout
innodb_lock_wait_timeout
Global
No
Permitted Values
Type
numeric
Default
50
Range
1 .. 1073741824
transaction may wait for a row lock before giving up. The default
InnoDB
InnoDB
[1249] option, available as of MySQL 5.0.32. See also
Error Handling".)
[1244] applies to
and this timeout does not apply to waits for table locks.
--innodb_locks_unsafe_for_binlog
innodb_locks_unsafe_for_binlog
Yes,
innodb_locks_unsafe_for_binlog
innodb_locks_unsafe_for_binlog
Global
No
5.6.3
1244
Recovery".
[1244]
rolled back the entire transaction if a lock
row locks only. A MySQL table lock does
InnoDB
InnoDB
--
[1244]