~~REDIRECT>percona-server:features:suppress_log_warning_1592~~

====== Patch: suppress_log_warning_1592 ======

In some [[http://bugs.mysql.com/bug.php?id=42851 |circumstances]] MySQL will warn you that a statement is unsafe to replicate whereas it is perfectly safe:
<code>090213 16:58:54 [Warning] Statement is not safe to log in statement format.</code>
This has no effect on replication (see the discussion on MySQL's bugzilla) but it can fill up your error log with unnecessary messages. 

This patch 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 from MySQL 5.1.37, but this bug still appears in some situations.

:!: 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.

===== Version-Specific Information =====

^ Percona-Server Version ^ Comments ^
| [[http://www.percona.com/docs/wiki/percona-server:release_notes_51#release_5147-110|5.1.47-11.0]] | Full functionality available. |

===== Variables Provided =====

==== suppress_log_warning_1592 ====

|     Type|System and command-line variable|
|    Scope|Global|
|  Dynamic|Yes|
|  Default|OFF|

Disables warning #1592 (unsafe statement for binary logging).

===== Related Reading =====

  * [[http://bugs.mysql.com/bug.php?id=42851 |MySQL bug 42851]]
  * [[http://dev.mysql.com/doc/refman/5.1/en/innodb-and-mysql-replication.html|MySQL InnoDB replication]]
  * [[http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html|InnoDB Startup Options and System Variables]]
  * [[http://dev.mysql.com/doc/refman/5.1/en/innodb-error-handling.html|InnoDB Error Handling]]