While I've used MySQL casually for quite a while (my license dates to
early 2000), I've never used it for a heavy, mission-critical load
where IT policies hadn't already been set for me. Which I'm about to.
My natural inclination, from three decades of db work and general
wizardry, is to packrat. Keep each day's general log in a dated file,
e.g., archive foo.log to foo.20071226. Hang onto at least a few
months' worth, if it turns out to be untenable to keep them forever.
This is easy enough to do, but I wonder why it doesn't come up in
discussion as a reasonable or best practice. Checking my archives
here, the MySQL forums, the manual, Dubois, and Kruckenberg/Pipes,
there's some talk of mysql-log-rotate but nothing about dated files
or retaining them beyond a ten-day window.
Yet it's a well-known and useful practice with other software, e.g., Apache's
CustomLog "| rotatelogs access.%Y%m%d 86400" combined
Am I missing something? Is there a reason why longish-term archiving
of log files doesn't make sense?
-- David Lubkin.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
