content_image/732361.jpg
<img src='content_image/732361.jpg'>

When a warning is produced by the determination, a standard MySQL warning is produced (and is available using SHOW WARNINGS ). The information is also written to the mysqld  error log. Only one error for each error instance per client connection is logged to prevent flooding the log. The log message includes the SQL statement that was attempted. 

If a replica has log_error_verbosity  set to display warnings, the replica prints messages to the error log to provide information about its status, such as the binary log and relay log coordinates where it starts its job, when it is switching to another relay log, when it reconnects after a disconnect, statements that are unsafe for statement-based logging, and so forth. 

## 5.4.4.4 Logging Format for Changes to mysql Database Tables 

The contents of the grant tables in the mysql  database can be modified directly (for example, with INSERT or DELETE ) or indirectly (for example, with GRANT  or CREATE USER ). Statements that affect mysql database tables are written to the binary log using the following rules: 

•Data manipulation statements that change data in mysql  database tables directly are logged according to the setting of the binlog_format  system variable. This pertains to statements such as INSERT , UPDATE , DELETE , REPLACE , DO , LOAD DATA , SELECT , and TRUNCATE TABLE . 

•Statements that change the mysql  database indirectly are logged as statements regardless of the value of binlog_format . This pertains to statements such as GRANT , REVOKE , SET PASSWORD , RENAME USER , CREATE  (all forms except CREATE TABLE ... SELECT ), ALTER  (all forms), and DROP  (all forms). 

