mysqlbinlog — Utility for Processing Binary Log Files • --base64-output= value • AUTO  ("automatic") or  UNSPEC  ("unspecified") displays  BINLOG  statements automatically when necessary (that is, for format description events and row events). If no  --base64-output  option is given, the effect is the same as  --base64-output=AUTO . • NEVER  causes  BINLOG  statements not to be displayed.  mysqlbinlog  exits with an error if a row event is found that must be displayed using  BINLOG . • DECODE-ROWS  specifies to  mysqlbinlog  that you intend for row events to be decoded and displayed as commented SQL statements by also specifying the  --verbose  option. Like  NEVER ,  DECODE-ROWS suppresses display of  BINLOG  statements, but unlike  NEVER , it does not exit with an error if a row event is found. • --bind-address= ip_address • --binlog-row-event-max-size= N • --character-sets-dir= dir_name • --compress This option determines when events should be displayed encoded as base-64 strings using  BINLOG statements. The option has these permissible values (not case-sensitive): Automatic  BINLOG  display is the only safe behavior if you intend to use the output of  mysqlbinlog  to re-execute binary log file contents. The other option values are intended only for debugging or testing purposes because they may produce output that does not include all events in executable form. For examples that show the effect of  --base64-output  and  --verbose  on row event output, see Section 4.6.9.2, “mysqlbinlog Row Event Display” . On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server. Specify the maximum size of a row-based binary log event, in bytes. Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256. The default is 4GB. The directory where character sets are installed. See Section 10.15, “Character Set Configuration” . Compress all information sent between the client and the server if possible. See Section 4.2.8, “Connection Compression Control” . This option was added in MySQL 8.0.17. As of MySQL 8.0.18 it is deprecated. Expect it to be removed in a future version of MySQL. See Configuring Legacy Connection Compression. 605 Command-Line Format --binlog-row-event-max-size=# Type Numeric Default Value 4294967040 Minimum Value 256 Maximum Value 18446744073709547520 Note