[MDEV-4693] FLUSH STATUS is reseting Subquery_cache_miss and Subquery_cache_hits global status variables Created: 2013-06-22  Updated: 2013-07-01  Resolved: 2013-07-01

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.31
Fix Version/s: 5.5.32

Type: Bug Priority: Trivial
Reporter: Jean Weisbuch Assignee: Sergei Golubchik
Resolution: Not a Bug Votes: 0
Labels: flush, subquery
Environment:

Debian Squeeze amd64


 Description   

Normally, only the SESSION status variables are flushed/reset when FLUSH STATUS is called but the Subquery_cache_hit and Subquery_cache_miss variables are globally reset (knowing that these status variables have the same value for the GLOBAL and SESSION scope).

MariaDB \[(none)]> SHOW GLOBAL STATUS LIKE 'Subquery_cache%'; FLUSH STATUS; SHOW GLOBAL STATUS LIKE 'Subquery_cache%';
 
+---------------------+-----------+
 
| Variable_name       | Value     |
 
+---------------------+-----------+
 
| Subquery_cache_hit  | 732043764 |
 
| Subquery_cache_miss | 46946161  |
 
+---------------------+-----------+
 
2 rows in set (0.00 sec)
 
 
 
Query OK, 0 rows affected (0.00 sec)
 
 
 
+---------------------+-------+
 
| Variable_name       | Value |
 
+---------------------+-------+
 
| Subquery_cache_hit  | 0     |
 
| Subquery_cache_miss | 0     |
 
+---------------------+-------+
 
2 rows in set (0.00 sec)



 Comments   
Comment by Elena Stepanova [ 2013-06-22 ]

Not judging whether it's a bug or not (I'll leave it to somebody else to decide it), just for a note – description of FLUSH STATUS says it may reset global variables:

<quote>
This option adds the current thread's session status variable values to the global values and resets the session values to zero. Some global variables may be reset to zero as well. It also resets the counters for key caches (default and named) to zero and sets Max_used_connections to the current number of open connections.
</quote>
http://dev.mysql.com/doc/refman/5.5/en/flush.html

Comment by Jean Weisbuch [ 2013-06-22 ]

You are right, its not a bug then as the global and session status are shared on this variable.

Generated at Thu Feb 08 06:58:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.