MySQL Bugs: #29278: log-output should default to FILE for backwards compliance.

Bug #29278	log-output should default to FILE for backwards compliance.
Submitted:	21 Jun 2007 18:51	Modified:	24 Jul 2007 1:46
Reporter:	Tobias Asplund	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Marc ALFF	CPU Architecture:	Any

Description:
Just upgrading will make slow logs, etc seem to "stop" logging, because they're not logging to files.
In cases where you just upgrade your server and don't get an instance of the slow_log and general_log tables it would just silently stop logging.

How to repeat:
filed on behalf of trudy:

22:03 <flupps|US> Sorry, I was somewhere else. The other thing is log-output defaulting to TABLE, so, a clean upgrade will suddenly "stop" logging from someone's perspective who hasn't read up on the log tables and new defaults
22:04 <flupps|US> general log is probably not a big issue, since most have it disabled, but the slow log could be bad
22:04 <trudy|away> flupps|US: i believe that's being addressed. i seem to recall some discussion about that at the runtime meting earlier this month
22:04 <flupps|US> Since many people use it regularly as a metric of how their servers are doing, and monitor their size
22:04 <flupps|US> oh, okay :)
22:05 <flupps|US> sounds terrific :)
22:05 <trudy|away> um ... can i ask you to file a bug on that? can't remember if one already exists. it would be a good reminder to us.

Duplicate of Bug#29993

(Normally, the older bug is kept, but work for 29993 was already in progress
when this duplicate was found, so closing this report instead).