mysqlbinlog — Utility for Processing Binary Log Files • --compression-algorithms= value • --connection-server-id= server_id • --database= db_name ,  -d  db_name •While  db_name  is the default database, statements are output whether they modify tables in  db_name or a different database. •Unless  db_name  is selected as the default database, statements are not output, even if they modify tables in  db_name . •There is an exception for  CREATE DATABASE ,  ALTER DATABASE , and  DROP DATABASE . The database being  created, altered, or dropped  is considered to be the default database when determining whether to output the statement. The permitted compression algorithms for connections to the server. The available algorithms are the same as for the  protocol_compression_algorithms  system variable. The default value is uncompressed . For more information, see Section 4.2.8, “Connection Compression Control” . This option was added in MySQL 8.0.18. --connection-server-id  specifies the server ID that  mysqlbinlog  reports when it connects to the server. It can be used to avoid a conflict with the ID of a replica server or another  mysqlbinlog process. If the  --read-from-remote-server  option is specified,  mysqlbinlog  reports a server ID of 0, which tells the server to disconnect after sending the last log file (nonblocking behavior). If the  --stop- never  option is also specified to maintain the connection to the server,  mysqlbinlog  reports a server ID of 1 by default instead of 0, and  --connection-server-id  can be used to replace that server ID if required. See Section 4.6.9.4, “Specifying the mysqlbinlog Server ID” . This option causes  mysqlbinlog  to output entries from the binary log (local log only) that occur while db_name  is been selected as the default database by  USE . The  --database  option for  mysqlbinlog  is similar to the  --binlog-do-db  option for  mysqld , but can be used to specify only one database. If  --database  is given multiple times, only the last instance is used. The effects of this option depend on whether the statement-based or row-based logging format is in use, in the same way that the effects of  --binlog-do-db  depend on whether statement-based or row- based logging is in use. Statement-based logging.   The  --database  option works as follows: Suppose that the binary log was created by executing these statements using statement-based-logging: INSERT INTO test.t1 (i) VALUES(100); INSERT INTO db2.t2 (j) VALUES(200); USE test; INSERT INTO test.t1 (i) VALUES(101); INSERT INTO t1 (i) VALUES(102); INSERT INTO db2.t2 (j) VALUES(201); USE db2; INSERT INTO test.t1 (i) VALUES(103); INSERT INTO db2.t2 (j) VALUES(202); INSERT INTO t2 (j) VALUES(203); 606