Changing max_slowlog_size to 0 does not turn off Slow Query Log Rotation
Bug #1687964 reported by
Robert Golebiowski
This bug report is a duplicate of:
Bug #1704056: Enabling and disabling slow query log rotation spuriously adds version suffix to the next slow query log file name.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.5 |
New
|
Undecided
|
Unassigned | |||
| 5.6 |
New
|
Undecided
|
Unassigned | |||
| 5.7 |
New
|
Undecided
|
Vishal kasle | |||
Bug Description
Changing max_slowlog_size to value > 0 turns on Slow Query Log Rotation. Sequential number gets added to a log name on each log rotation. As output we get a series of slow query log files : log_name.000001, log_name.000002 etc. When we change the max_slowlog_size back to 0 and change the name of the slow query log to (for instance) new_log we will get: new_log.000001, although Slow Query Log rotation has been disabled. The fix would be disable adding extension to slow query log name when feature gets disabled (i.e. max_slowlog_size gets changed to 0).
| tags: | added: slow-extended |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #1 |
To post a comment you must log in.
I have missed this bug now and logged it again as bug 1704056. As the latter has the testcase and fix, closing this one as its duplicate