Oracle 5.0 Reference Manual page 1491

Replication and Binary Logging Options and Variables
This option is used internally by the MySQL test suite for replication testing and debugging.
•
--sporadic-binlog-dump-fail
Command-Line Format
Option-File Format
This option is used internally by the MySQL test suite for replication testing and debugging.
System variables used with the binary log.
controlling binary logging. They can be set at server startup and some of them can be changed at
runtime using SET. Server options used to control binary logging are listed earlier in this section.
• [1471]
log_bin
Variable Name
Variable Scope
Dynamic Variable
Whether the binary log is enabled. If the
variable is ON; otherwise it is OFF. This variable reports only on the status of binary logging (enabled
or disabled); it does not actually report the value to which
See Section 5.2.3, "The Binary
•
log_slave_updates
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Whether updates received by a slave server from a master server should be logged to the slave's
own binary log. Binary logging must be enabled on the slave for this variable to have any effect. See
Section 16.1.2.3, "Replication Slave Options and
•
max_binlog_cache_size
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Default
0
[1471]
--sporadic-binlog-dump-fail
sporadic-binlog-dump-fail
Permitted Values
Type
boolean
Default
FALSE
The following list describes system variables for
log_bin
Global
No
--log-bin
Log".
[1471]
--log-slave-updates
log_slave_updates
Yes,
log_slave_updates
log_slave_updates
Global
No
Permitted Values
Type
boolean
Default
FALSE
[1471]
--max_binlog_cache_size=#
max_binlog_cache_size
Yes,
max_binlog_cache_size
1471
max_binlog_cache_size
[1467] option is used, then the value of this
[1467]
--log-bin
[1471]
Variables".
[1471]
is set.