MySQL Bugs: #43159: Log entry should be added when Purge runs

Bug #43159	Log entry should be added when Purge runs
Submitted:	24 Feb 2009 19:38	Modified:	4 Mar 2009 10:47
Reporter:	Kolbe Kegel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Eric Herman	CPU Architecture:	Any

Description:
MEM should add a Log entry each time data is purged. The log entry should note how many rows of each type of data were purged (historical data, logs, quan data).

How to repeat:
n/a

Suggested fix:
Implement feature as described.

branches/2.0/:

revno: 6608
revision-id: jsled@asynchronous.org-20090227222408-xwwdyil34gv907sg
parent: jsled@asynchronous.org-20090227222217-hgt4nlo8jki53s6w
committer: Josh Sled <jsled@asynchronous.org>
branch nick: 2.0
timestamp: Fri 2009-02-27 17:24:08 -0500
message:
  [merge from trunk] Bug#43159 CSC#33910 : purge logging
  BUG#43159 CSC#33910 add table name and rows deleted to the debug timing info
  BUG#43159 CSC#33910 Purging now logs number of rows deleted if greater than zero or if debug logging is enabled. http://bugs.mysql.com/bug.php?id=43159

Patch installed in versions => 2.0.5.7148.

verified log entries are added in build 2.0.5.7148

An entry was added to the 2.0.5 changelog:

MySQL Enterprise Monitor did not add a log entry each time data was purged. The log entry should have noted how many rows of each type of data were purged (historical data, logs, quan data).