On 7/18/09 1:52 PM, Luis Soares wrote:
> #At file:///home/lsoares/Workspace/mysql-server/bugfix/b42851/mysql-5.1-bugteam/
> based on revid:joro@stripped
>
> 3024 Luis Soares 2009-07-18
> BUG#42851: Spurious "Statement is not safe to log in statement
> format." warnings
>
> Several warnings are printed when using statement based logging
> and unsafe operations are logged to the binlog. For example, this
> is the case for statements using LIMIT + ORDER BY PK. As a
> consequence, this would rapidly increase mysqld error log size,
> in some cases to several gigabytes, causing a maintenance
> nightmare.
>
> This patch proposes a mechanism to selectively and voluntarily
> suppress warnings from mysqld error log. It adds a dynamic server
> variable "suppress_log_warnings", which can be used to set/reset
> warning filtering from mysqld error log. Its details are the
> following:
[..]
Excuse my ignore, what part of this patch can't be done by piping the
error log through a filter script? AFAIR, its possible to have a pipe as
a logging target.
Also, wouldn't it be much simpler to just rate limit messages?
