Oracle 5.0 Reference Manual page 1270

Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
In MySQL 5.0.13 and up,
default. If
--innodb_rollback_on_timeout
to abort and roll back the entire transaction (the same behavior as before MySQL 5.0.13).
InnoDB
This variable was added in MySQL 5.0.32.
•
innodb-safe-binlog
Version Removed
Version Deprecated
Command-Line Format
Option-File Format
Deprecated
If this option is given, then after a crash recovery by InnoDB,
the last not-rolled-back transaction in the log. The option also causes
binary log is smaller or shorter than it should be. See
was removed in MySQL 5.0.3, having been made obsolete by the introduction of XA transaction
support. You should set
innodb_support_xa
•
innodb_support_xa
Version Introduced
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Enables support for two-phase commit in XA transactions, causing an extra disk flush for
InnoDB
transaction preparation. This setting is the default. The XA mechanism is used internally and is
essential for any server that has its binary log turned on and is accepting changes to its data from
more than one thread. If you turn it off, transactions can be written to the binary log in a different
order from the one in which the live database is committing them. This can produce different data
when the binary log is replayed in disaster recovery or on a replication slave. Do not turn it off on a
Startup Options and System Variables
InnoDB
innodb_rollback_on_timeout
Yes,
innodb_rollback_on_timeout
innodb_rollback_on_timeout
Global
No
Permitted Values
Type
boolean
Default
OFF
rolls back only the last statement on a transaction timeout by
InnoDB
5.0.3
5.0.3
--innodb-safe-binlog
innodb-safe-binlog
5.0.3
Permitted Values
Type
boolean
innodb_support_xa
[1250].
5.0.3
--innodb_support_xa
innodb_support_xa
Yes,
innodb_support_xa
innodb_support_xa
Global, Session
Yes
Permitted Values
Type
boolean
Default
TRUE
1250
[1249]
[1249] is specified, a transaction timeout causes
truncates the binary log after
mysqld
InnoDB
Section 5.2.3, "The Binary
[1250] to or 1 to ensure consistency. See
ON
[1250]
to print an error if the
Log". This variable