#At file:///home/thek/Development/cpp/mysqlbzr/mysql-5.1-bug38066/
2745 Kristofer Pettersson 2008-09-29
Bug#38066 Events log 'note' level messages by default in the error log
The event scheduler logged start-, stop-execution messages in the error log
on lowest log-warning level which would lead to very large log files in
a short time.
This patch changes this behavior so that these messages only are logged if
the log-warning level is high enough (>1).
modified:
sql/event_scheduler.cc
per-file messages:
sql/event_scheduler.cc
* Only output start-, end-execution messages if log level is high enough.
=== modified file 'sql/event_scheduler.cc'
--- a/sql/event_scheduler.cc 2007-11-14 11:25:43 +0000
+++ b/sql/event_scheduler.cc 2008-09-29 14:10:17 +0000
@@ -301,11 +301,12 @@ Event_worker_thread::run(THD *thd, Event
goto end;
}
- sql_print_information("Event Scheduler: "
- "[%s].[%s.%s] started in thread %lu.",
- job_data.definer.str,
- job_data.dbname.str, job_data.name.str,
- thd->thread_id);
+ if (thd->variables.log_warnings > 1)
+ sql_print_information("Event Scheduler: "
+ "[%s].[%s.%s] started in thread %lu.",
+ job_data.definer.str,
+ job_data.dbname.str, job_data.name.str,
+ thd->thread_id);
thd->enable_slow_log= TRUE;
@@ -318,7 +319,7 @@ Event_worker_thread::run(THD *thd, Event
"[%s].[%s.%s] event execution failed.",
job_data.definer.str,
job_data.dbname.str, job_data.name.str);
- else
+ else if (thd->variables.log_warnings >1)
sql_print_information("Event Scheduler: "
"[%s].[%s.%s] executed successfully in thread %lu.",
job_data.definer.str,
