Oracle 5.0 Reference Manual page 1476

Table of Contents

Advertisement

Replication and Binary Logging Options and Variables
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
The name to use for the relay log index file. The default name is
the data directory, where
Due to the manner in which MySQL parses server options, if you specify this option, you must supply
a value; the default basename is used only if the option is not actually specified. If you use the
relay-log-index
this behavior depends on the other options used, the order in which they are specified, and whether
they are specified on the command line or in an option file. For more information about how MySQL
handles server options, see
If you specify this option, the value specified is also used as the basename for the relay logs. You
can override this behavior by specifying a different relay log file basename using the
[1455]
option.
log
--relay-log-info-file=file_name
Command-Line Format
Option-File Format
Option Sets Variable
The name to use for the file in which the slave records information about the relay logs. The default
name is
relay-log.info
Section 16.2.2.2, "Slave Status
--relay-log-purge={0|1}
Disable or enable automatic purging of relay logs as soon as they are no longer needed. The default
value is 1 (enabled). This is a global variable that can be changed dynamically with
relay_log_purge =
--relay-log-space-limit=size
This option places an upper limit on the total size in bytes of all relay logs on the slave. A value
of 0 means "no limit." This is useful for a slave server host that has limited disk space. When the
limit is reached, the I/O thread stops reading binary log events from the master server until the
SQL thread has caught up and deleted some unused relay logs. Note that this limit is not absolute:
There are cases where the SQL thread needs more events before it can delete relay logs. In that
case, the I/O thread exceeds the limit until it becomes possible for the SQL thread to delete some
relay logs because not doing so would cause a deadlock. You should not set
[1456]
space-limit
[1472]
binlog-size
the I/O thread waits for free space because
--relay-log-index=name
relay-log-index
Yes,
relay_log_index
relay-log-index
Global
No
Permitted Values
Type
file name
is the name of the slave server.
host_name
[1455]
option without specifying a value, unexpected behavior is likely to result;
Section 4.2.3, "Specifying Program
--relay-log-info-file=file_name
relay-log-info-file
Yes,
relay_log_info_file
Permitted Values
Type
file name
Default
relay-log.info
in the data directory. For information about the format of this file, see
Logs".
[1456]
N.
[1456]
to less than twice the value of
if
--max-relay-log-size
1456
[1464]
host_name-relay-bin.index
Options".
[1456]
[1465]
--max-relay-log-size
[1455]
is 0). In that case, there is a chance that
--relay-log-space-limit
--
--relay-
SET GLOBAL
--relay-log-
[1455]
(or
--max-
[1456]
is exceeded, but
in

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mysql 5.0

Table of Contents