This feature is intended to provide a general mechanism (using log_warnings_silence) to disable certain warning messages to the log file. Currently, it is only implemented for disabling message #1592 warnings. This feature does not influence warnings delivered to a client.
ON(=‘1592’) / OFF
This has no effect on replication, but it can fill up your error log with unnecessary messages. This variable allows you to completely disable logging of this warning.
NOTE: Only MySQL 5.1 is subject to this bug. A partial solution has been published beginning with MySQL 5.1.37, but this bug still appears in some situations.
When ON, disables reporting of warning #1592 (unsafe statement for binary logging).
All warnings #1592 will be disabled, so you will not be able to know if your statements are really safe to replicate anymore. Use it at your own risk and only if you understand what you are doing.
In some circumstances, MySQL will warn you that a statement is unsafe to replicate even though it is perfectly safe. For example, in versions lower than 5.1.59, the warning will look like:
090213 16:58:54 [Warning] Statement is not safe to log in statement format.
or in versions 5.1.59 or higher:
010214 12:08:52 [Warning] Statement may not be safe to log in statement format.
For general inquiries about our open source software and database management tools, please send us your question and someone will contact you.