Oracle 5.0 Reference Manual page 365

mysqlbinlog
INSERT INTO t2 (j)
mysqlbinlog --database=test
is no default database. It outputs the three
three statements following
INSERT
mysqlbinlog --database=db2
is no default database. It does not output the three
does output the three
•
--debug[=debug_options]
Write a debugging log. A typical
'd:t:o,/tmp/mysqlbinlog.trace'.
•
--disable-log-bin
Disable binary logging. This is useful for avoiding an endless loop if you use the
[347] option and are sending the output to the same MySQL server. This option also is useful
log
when restoring after a crash to avoid duplication of the statements you have logged.
This option requires that you have the
a
SET sql_log_bin = 0
The statement is ineffective unless you have the
SET
• [345],
--force-read
With this option, if
mysqlbinlog
warning, ignores the event, and continues. Without this option,
an event.
• [345],
--hexdump -H
Display a hex dump of the log in comments. The hex output can be helpful for replication debugging.
Hex dump format is discussed later in this section. This option was added in MySQL 5.0.16.
•
--host=host_name
Get the binary log from the MySQL server on the given host.
•
--local-load=path
Prepare local temporary files for
Important
These temporary files are not automatically removed by
any other MySQL program.
• [345],
--offset=N
Skip the first entries in the log.
N
•
--password[=password]
The password to use when connecting to the server. If you use the short option form (-p), you
cannot have a space between the option and the password. If you omit the
following the
--password
one.
Specifying a password on the command line should be considered insecure. See
"End-User Guidelines for Password
password on the command line.
— Utility for Processing Binary Log Files
VALUES(203);
does not output the first two
INSERT
USE db2.
does not output the first two
statements following
INSERT
[345],
-# [debug_options]
debug_options
[345],
-D
SUPER
statement in its output to disable binary logging of the remaining output.
-f
reads a binary log event that it does not recognize, it prints a
[345],
-h host_name
[345],
-l path
LOAD DATA INFILE
-o N
[345],
-p[password]
[345] or option on the command line,
-p
Security". You can use an option file to avoid giving the
345
INSERT
statements following
INSERT
statements following
INSERT
USE db2.
string is 'd:t:o,file_name'. The default is
[578] privilege. It causes
[578] privilege.
SUPER
mysqlbinlog
in the specified directory.
mysqlbinlog
statements because there
test, but not the
USE
statements because there
test, but
USE
--to-last-
to include
mysqlbinlog
stops if it reads such
or
mysqlbinlog
value
password
prompts for
Section 6.1.2.1,