Oracle 5.0 Reference Manual page 566

bin
behaviors were restored in MySQL 5.0.54. (See Bug #28603 and Bug #28597.)
If you supply an extension in the log name (for example,
bin=base_name.extension
appends a numeric extension to the binary log basename to generate binary log file
mysqld
names. The number increases each time the server creates a new log file, thus creating an ordered
series of files. The server creates a new file in the series each time it starts or flushes the logs.
The server also creates a new binary log file automatically after the current log's size reaches
[1472]. A binary log file may become larger than
max_binlog_size
you are using large transactions because a transaction is written to the file in one piece, never split
between files.
To keep track of which binary log files have been used,
contains the names of all used binary log files. By default, this has the same basename as the binary
log file, with the extension '.index'. You can change the name of the binary log index file with the
log-bin-index[=file_name]
running; doing so would confuse mysqld.
The term "binary log file" generally denotes an individual numbered file containing database events.
The term "binary log" collectively denotes the set of numbered binary log files plus the index file.
A client that has the
SUPER
a
SET sql_log_bin=0
The server evaluates the
the same way as it does the
options. For information about how this is done, see
Replication and Binary Logging
A replication slave server by default does not write to its own binary log any data modifications that
are received from the replication master. To log these modifications, start the slave with the
[1451]
slave-updates
"Replication Slave Options and
other slaves in chained replication.
You can delete all binary log files with the
LOGS. See Section 13.7.6.5,
BINARY
Syntax".
If you are using replication, you should not delete old binary log files on the master until you are sure
that no slave still needs to use them. For example, if your slaves never run more than three days
behind, once a day you can execute
logs that are more than three days old. You can remove the files manually, but it is preferable to use
LOGS, which also safely updates the binary log index file for you (and which can take
PURGE BINARY
a date argument). See
You can display the contents of binary log files with the
you want to reprocess statements in the log for a recovery operation. For example, you can update a
MySQL server from the binary log as follows:
shell> mysqlbinlog log_file | mysql -h server_name
also can be used to display replication slave relay log file contents because they are
mysqlbinlog
written using the same format as binary log files. For more information on the
how to use it, see Section 4.6.7,
information about the binary log and recovery operations, see
Recovery Using the Binary
The Binary Log
[1467] options was treated as absolute rather than relative. The previous
[1467]), the extension is silently removed and ignored.
[1468] option. You should not manually edit this file while
[578] privilege can disable binary logging of its own statements by using
statement. See Section 5.1.4, "Server System
[1469]
--binlog-do-db
--replicate-do-db
Options".
option in addition to the
Variables"). This is done when a slave is also to act as a master to
RESET MASTER
"RESET
mysqladmin flush-logs
Section 13.4.1.1, "PURGE BINARY LOGS
"mysqlbinlog
Log".
546
--log-
also creates a binary log index file that
mysqld
and
--binlog-ignore-db
[1457] and
--replicate-ignore-db
Section 16.2.3.1, "Evaluation of Database-Level
[1467] option (see
--log-bin
statement, or a subset of them with
Syntax", and Section 13.4.1.1,
on the master and then remove any
Syntax".
mysqlbinlog
— Utility for Processing Binary Log
Section 7.5, "Point-in-Time (Incremental)
[1472]
max_binlog_size
Variables".
[1470] options in
--log-
Section 16.1.2.3,
"PURGE BINARY LOGS
utility. This can be useful when
mysqlbinlog
Files". For more
if
--
is
mysqld
[1457]
PURGE
utility and