Bug #57109 Loading database with log_bin turned on takes too much space

• Submitted: 29 Sep 2010 16:55
• Modified: 4 Nov 2010 10:50
• Reporter: Kevin Benton
• Status: Verified
• Category: MySQL Server: Command-line Clients
• Severity: S4 (Feature request)
• Version: 5.1.41, ndb 7.0.13
• OS: Linux
• CPU Architecture: Any

[29 Sep 2010 16:55] Kevin Benton

Description:
We need the ability to change the log_bin variable on the global level in a running server given the appropriate permissions (i.e. SUPER). This would allow us to reload a database from a dump file without worrying about space considerations. It would also be extremely helpful if a new command like...

CLEAR [ALL|BINARY|ERROR|SLOW] LOGS

were available so that automation could handle loading a database from

mysqldump --server-read-only --no-log-bin --clear-all-logs ... | mysql ...

without taking up way too much space when being loaded daily. This makes it possible for an authorized user to do this type of action without having to become the mysql user in order to remove any logs.

With this capability, it would greatly help those who rely on continuous integration to test their environments and work with reference data sets along with test fixtures to do those tests. In the event of a failure, those logs would provide the necessary data to troubleshoot issues in isolation. It also makes it possible to keep the amount of logging down to a reasonable level because it would be removed by authorized individuals through mysqld.

How to repeat:
See Description.

Suggested fix:
See Description.