Bug #33737 | PURGE MASTER LOGS works only if log-bin option enabled in my.cnf | ||
---|---|---|---|
Submitted: | 8 Jan 2008 10:11 | Modified: | 13 Jan 2008 11:39 |
Reporter: | Maciej Dobrzanski | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 4.1+ | OS: | Any |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
Tags: | binary logs |
[8 Jan 2008 10:11]
Maciej Dobrzanski
[8 Jan 2008 10:12]
Magnus BlÄudd
Probably expected behaviour
[8 Jan 2008 11:59]
Hartmut Holzgraefe
I'd say expected behavior, too, as without an active "log-bin" it is not clear what the base name for binlog files is supposed to be, and just removing files based on the default "$hostname-bin" basename doesn't seem to be the right IMHO.
[8 Jan 2008 14:41]
Valeriy Kravchuk
I think this is a reasonable documentation request. http://dev.mysql.com/doc/refman/5.1/en/purge-master-logs.html should include a note about this.
[10 Jan 2008 21:34]
Stefan Hinz
We can document this, but it seems odd that the PURGE MASTER LOGS statement returns with no error (or at least a warning) when it obviously does not do what it can reasonably be expected to do. I'd suggest to document it, then reset the bug to Open and change the category to Server:Replication.
[13 Jan 2008 11:39]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.