Oracle 5.0 Reference Manual page 491

Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
If a write by a replication slave to its relay log causes the current log file size to exceed the value
of this variable, the slave rotates the relay logs (closes the current file and opens the next one).
If
max_relay_log_size
binary log and the relay log. If
the size of the relay log, which enables you to have different sizes for the two logs. You must set
max_relay_log_size
value is 0. See Section 16.2.1, "Replication Implementation
•
max_seeks_for_key
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Limit the assumed maximum number of seeks when looking up rows based on a key. The MySQL
optimizer assumes that no more than this number of key seeks are required when searching for
matching rows in a table by scanning an index, regardless of the actual cardinality of the index (see
Section 13.7.5.18, "SHOW INDEX
MySQL to prefer indexes instead of table scans.
•
max_sort_length
Server System Variables
--max_relay_log_size=#
max_relay_log_size
Yes,
max_relay_log_size
max_relay_log_size
Global
Yes
Permitted Values
Type
numeric
Default
0
Range
0 .. 1073741824
[470] is 0, the server uses
max_relay_log_size
[470] to between 4096 bytes and 1GB (inclusive), or to 0. The default
[471]
--max_seeks_for_key=#
max_seeks_for_key
Yes,
max_seeks_for_key
max_seeks_for_key
Global, Session
Yes
Permitted Values
Platform
32
Bit Size
Type
numeric
Default
4294967295
Range
1 .. 4294967295
Permitted Values
Platform
64
Bit Size
Type
numeric
Default
18446744073709547520
Range
1 .. 18446744073709547520
Syntax"). By setting this to a low value (say, 100), you can force
[471]
471
[470]
[1472]
max_binlog_size
[470] is greater than 0, it constrains
Details".
[471]
for both the