mySQL log file exceeding 270MB! What's up?

[gheffron]

My host has just informed me that I'm about to exceed my allowed limit of 300MB after my recent install of OSCommerce. They're saying that the mySQL log file is 270MB, and that if I cut it down, everything will be all right.

Is this normal for my log file to be that large? It seems quite weird. Also, does anyone know how to "cut it down" without disrupting anything?
Thanks,
Greg Heffron

[jpf]

It is save to delete your MySQL log - Turn off the logging in OSC - it is only best for debugging...

Every person that view EACH page could produce anywhere from 2 to 20 or more SQL commands. When Logging SQL - EACH command is copied into this file and can grow QUITE FAST on a LIVE "busy" site (even though you get few to no orders).

How long has the site been live? - 270 MB is quite large.

[gheffron]

I found out that the logging that you can turn off in OSC isn't the same log. In fact, I had to ask my server administrator to turn off mySQL's logging directly, as I didn't have telnet access or anything. So far, it worked like a charm.

One note: don't ever delete your log file. Instead, use the mySQL command, "flush-logs."