Oracle 5.0 Reference Manual page 1488

Replication and Binary Logging Options and Variables
Option-File Format
Variable Name
Variable Scope
Dynamic Variable
Enable binary logging. The server logs all statements that change data to the binary log, which is
used for backup and replication. See
The option value, if given, is the basename for the log sequence. The server creates binary log files
in sequence by adding a numeric suffix to the basename. It is recommended that you specify a
basename (see Section C.5.8, "Known Issues in
as the basename.
host_name-bin
Setting this option causes the
basename. This is a known issue; see Bug #19614 for more information.
•
--log-bin-index[=file_name]
Command-Line Format
Option-File Format
The index file for binary log file names. See
file name, and if you did not specify one with
as the file name.
bin.index
•
--log-bin-trust-function-creators[={0|1}]
Version Introduced
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
This option sets the corresponding
system variable. If no argument is given, the option sets the variable to 1.
log_bin_trust_function_creators
function and trigger creation. See
This option was added in MySQL 5.0.16.
•
--log-bin-trust-routine-creators[={0|1}]
log-bin
log_bin
Global
No
Permitted Values
Type
file name
Default
OFF
Section 5.2.3, "The Binary
MySQL", for the reason). Otherwise, MySQL uses
[1471] system variable to be set to
log_bin
[1468]
--log-bin-index=name
log-bin-index
Permitted Values
Type
file name
Default
OFF
Section 5.2.3, "The Binary
--log-bin
5.0.16
--log-bin-trust-function-creators
log-bin-trust-function-creators
Yes,
log_bin_trust_function_creators
log_bin_trust_function_creators
Global
Yes
Permitted Values
Type
boolean
Default
FALSE
log_bin_trust_function_creators
[463] affects how MySQL enforces restrictions on stored
Section 18.6, "Binary Logging of Stored
1468
Log".
ON
Log". If you omit the
[1467], MySQL uses
[1468]
[463]
[463]
Programs".
[1468]
(or 1), and not to the
host_name-