Bug #31533 general_log table grows with no limitations (possible auto-cleanup event)
Submitted: 11 Oct 2007 13:44 Modified: 28 Oct 2007 13:45
Reporter: Patrick Ancillotti Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Logging Severity:S4 (Feature request)
Version:5.1.22-rc OS:Linux
Assigned to: CPU Architecture:Any
Tags: general_log, mysqld general_log, sql logging
Triage: Triaged: D5 (Feature request)

[11 Oct 2007 13:44] Patrick Ancillotti
Description:
The MySQL 5.1.x logging to tables feature set seems to have no limitations in place, as this would be a new feature a lot of users wouldn't know that it would be there, or log in that format. To avoid having a MASSIVE log (i created a 30gb log over night, CSV doesn't scale well when you try work with it...)

How to repeat:
No way of really repeating, it's more a feature request

Suggested fix:
Create an event to automatically truncate data based on either a my.cnf setting (same as would be for the binary logging), or create an event to simply create an EVENT Scheduler Truncate for anything smaller than x days.
[28 Oct 2007 13:45] Valeriy Kravchuk
Thank you for a reasonable feature request.