Bug #15919 FLUSH STATUS should take an optional variable name to flush
Submitted: 22 Dec 2005 1:05 Modified: 25 Jan 2006 6:15
Reporter: J Rabbit Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:5.0.16 OS:Any (Any)
Assigned to: CPU Architecture:Any

[22 Dec 2005 1:05] J Rabbit 
Description:
It would be useful if the FLUSH STATUS command could take an optional argument of the particular status variable you would like to flush, rather than flushing everything it can.

Sometimes I do some DB maintenance that I know will cause the max_connections to spike whilst I run a slow query that locks tables. I'd like to be able to flush it back to zero afterwards so that later when I check the status I know if there have been any other spikes in the number of connections that I wasn't anticipating without disrupting the other status variables.

I'm sure there are other uses too.

How to repeat:
n/a

Suggested fix:
n/a
[25 Dec 2005 6:15] Valeriy Kravchuk 
Thank you for a feature request. This feature, if added, can be misused and may lead to inconsistent status reports. In other databases, for example, IBM Informix, similar performance indicies can be flushed only all at once. 

Why not just take into account the real situation when you get that status values? What do you think?
[26 Jan 2006 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".