If the mysqlbinlog utility is remote from the MySQL server where the binary logs reside, specify the location of the mysqlbinlog utility in the MYSQLBINLOG parameter of the MYSQL CAPI_CONNECTION statement or in the PATH environment variable.

MySQL binary log files contain events that describe database changes, including data changes and DDL changes. The term

binary log file

refers to an individual log file that contains database events and that has a unique name. The term

binary log

refers to a series of binary log files plus the index file that contains the names of the binary log files that have been used.

A binary log file name contains a base name and generated numeric suffix in the following format:

base_name

_binlog.

numeric_suffix

, for example, mysql_5_7_binlog.000001. The numeric suffix is incremented with each new log file.

When MySQL creates a new physical binary log file, it increments the numeric suffix in the log file name. MySQL creates a new log file under the following conditions:

If a MySQL server is restarted with a new binlog base name, a new series of binary logs starts. The first log file in the new series has a numeric suffix of 000001. Queries based on the online binary log file name will not return information about the previous binary logs. However, the previous binary logs and index file remain available on the server disk.