Oracle 5.0 Reference Manual page 1499

• If the value of
maximum relay log file size.
The SQL thread automatically deletes each relay log file as soon as it has executed all events in the
file and no longer needs it. There is no explicit mechanism for deleting relay logs because the SQL
thread takes care of doing so. However,
SQL thread deletes them.
16.2.2.2. Slave Status Logs
A replication slave server creates two logs. By default, these logs are files named
and
relay-log.info
be changed by using the
options, respectively. See
The two status logs contain information like that shown in the output of the
statement, which is discussed in
Because the status logs are stored on disk, they survive a slave server's shutdown. The next time the
slave starts up, it reads the two logs to determine how far it has proceeded in reading binary logs from
the master and in processing its own relay logs.
The master info log should be protected because it contains the password for connecting to the master.
See Section 6.1.2.3, "Passwords and
The slave I/O thread updates the master info log. The following table shows the correspondence
between the lines in the
Line in
master.info
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Replication Relay and Status Logs
max_relay_log_size
and created in the data directory. The names and locations of these files can
--master-info-file
Section 16.1.2, "Replication and Binary Logging Options and
Section 13.4.2, "SQL Statements for Controlling Slave
Logging".
master.info
SHOW SLAVE STATUS
Master_Log_File
Read_Master_Log_Pos
Master_Host
Master_User
Password (not shown by
STATUS)
Master_Port
Connect_Retry
Master_SSL_Allowed
Master_SSL_CA_File
Master_SSL_CA_Path
Master_SSL_Cert
Master_SSL_Cipher
Master_SSL_Key
[470] is 0,
max_binlog_size
rotates relay logs, which influences when the
FLUSH LOGS
[1453] and
--relay-log-info-file
file and the columns displayed by
Column Description
Number of lines in the file
The name of the master binary log currently
being read from the master
The current position within the master binary
log that have been read from the master
The host name of the master
The user name used to connect to the
master
The password used to connect to the master
SHOW SLAVE
The network port used to connect to the
master
The period (in seconds) that the slave will
wait before trying to reconnect to the master
Indicates whether the server supports SSL
connections
The file used for the Certificate Authority
(CA) certificate
The path to the Certificate Authority (CA)
certificates
The name of the SSL certificate file
The list of possible ciphers used in the
handshake for the SSL connection
The name of the SSL key file
1479
[1472] determines the
master.info
[1456]
Variables".
SHOW SLAVE STATUS
Servers".
SHOW SLAVE STATUS.