Bug #26671 record when mysqld server deleted binlogs
Submitted: 27 Feb 2007 9:00
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: General Severity:S4 (Feature request)
Version:* OS:Any
Assigned to: CPU Architecture:Any
Tags: expire_logs_days
Triage: Triaged: D5 (Feature request)

[27 Feb 2007 9:00] Shane Bester
Description:
it would be nice to have a line in the error log indicating when mysql deleted a binlog file.

it can be due to PURGE MASTER LOGS, RESET MASTER .. or FLUSH LOGS/server restart and expire_logs_days is enabled, for example.  Also max_binlog_size can be hit in combination with expire_logs_days.

currently it's impossible to determine if mysqld deleted the files, or if somebody manually deleted them.

How to repeat:
try figure out whether mysqld deleted a binlog or somebody did it manually (without the general query log on).

Suggested fix:
add a [note] to the mysqld error log indicating a binlog is deleted at this time with;

1) binlog filename
2) binlog size
3) binlog file timestamp