Bug #71760 com_flush is not specific enough

• Submitted: 18 Feb 2014 14:04
• Reporter: Oli Sennhauser
• Status: Open
• Category: MySQL Server
• Severity: S4 (Feature request)
• Version: 5.6.15
• OS: Any
• CPU Architecture: Any
• Tags: com_flush, flush, STATUS

[18 Feb 2014 14:04] Oli Sennhauser

Description:
The status com_flush counts all flush commands including:

FLUSH TABLES
FLUSH LOGS

and possibly some others.

For investigation purposes on problems it would make sense to distinguish between flush tables and flush logs and others.

The first can harm. The second possibly not.

How to repeat:
show global status like 'com%flush%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Com_flush     | 0     |
+---------------+-------+

flush logs;

show global status like 'com%flush%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Com_flush     | 1     |
+---------------+-------+

flush tables;

show global status like 'com%flush%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Com_flush     | 2     |
+---------------+-------+

Suggested fix:
status like

Com_flush_tables
Com_flush_logs (possibly separate binary, slow and general?)