Review rate limiting features for the slow query logging
Superseded by https:/
Current the slow query log rate limiting is implemented using a combination of two variables: log_slow_rate_type and log_slow_
The only thing actually needed is to have query sampling. Apparently this was implemented first, but "did not work as expected" (for all I know could have been a bug...) and then additional complexity with session limiting was piled on the top.
Thus let's revisit this for 5.6 and start with the actual desired thing: --slow-
Blueprint information
- Status:
- Complete
- Approver:
- Vadim Tkachenko
- Priority:
- Not
- Drafter:
- Laurynas Biveinis
- Direction:
- Needs approval
- Assignee:
- Laurynas Biveinis
- Definition:
- Superseded
- Series goal:
- Accepted for 5.6
- Implementation:
- Started
- Milestone target:
- None
- Started by
- Laurynas Biveinis
- Completed by
- Laurynas Biveinis
Related branches
Related bugs
Sprints
Whiteboard
is 0..100, default 100 - accept only integers or floats also?
intergers may be not enough.
We can make it floats, but I'm a bit wary of possible inexactiness. I.e. if 100.0 would still filter out some queries.
VT: so probably it should be --slow-
where N means how many queries to skip for logging ?
Laurynas: yes, it makes sense then.
Work Items
Dependency tree
* Blueprints in grey have been implemented.