Bug #25524 | under health tab, numerous status variables report incorrect values | ||
---|---|---|---|
Submitted: | 10 Jan 2007 16:29 | Modified: | 11 Jan 2007 15:36 |
Reporter: | david huhncke | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.2.8 | OS: | |
Assigned to: | CPU Architecture: | Any |
[10 Jan 2007 16:29]
david huhncke
[11 Jan 2007 9:56]
Valeriy Kravchuk
What version of MySQL server are you connecting to? If it is 5.0.x, SHOW STATUS shoes your SESSION status (that is, mostly actionbs of your particilar session). Please, compare SHOW GLOBAL STATUS results to values in MySQL Administrator.
[11 Jan 2007 14:36]
david huhncke
the mysql> show status; command only shows your session info in mysql 5 you need to perform mysql>show global status; values are now closer to reflect the values in mysqladmin, also repeated clicking of the refresh button increments created_tmp_tables value if this is normal i guess its not a bug
[11 Jan 2007 15:36]
Valeriy Kravchuk
Yes, it is normal. This is how SHOW STATUS works (via temp. table). MySQL Administrator just use SHOW GLOBAL STATUS. Look: mysql> show status like 'created_tmp%'; +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Created_tmp_disk_tables | 0 | | Created_tmp_files | 5 | | Created_tmp_tables | 6 | +-------------------------+-------+ 3 rows in set (0.00 sec) mysql> show status like 'created_tmp%'; +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Created_tmp_disk_tables | 0 | | Created_tmp_files | 5 | | Created_tmp_tables | 7 | +-------------------------+-------+ 3 rows in set (0.01 sec) mysql> show global status like 'created_tmp%'; +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Created_tmp_disk_tables | 0 | | Created_tmp_files | 5 | | Created_tmp_tables | 8 | +-------------------------+-------+ 3 rows in set (0.00 sec) Closing this report as not a bug.