[MDEV-3883] Show global status not in order Created: 2012-11-26  Updated: 2013-01-09  Resolved: 2013-01-09

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.28
Fix Version/s: 10.0.1, 5.5.29

Type: Bug Priority: Trivial
Reporter: Joffrey MICHAIE (Inactive) Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux Ubuntu


 Description   

Hi,

This is the first time I see this, when watching the show global status, some columns do not start with a capital letter, and are then displayed at the end ...

mariadb> SHOW GLOBAL STATUS;
 
(...)
 
| Uptime_since_flush_status                | 1474386          |
 
| binlog_commits                           | 0                |
 
| binlog_group_commits                     | 0                |
 
| binlog_snapshot_file                     | mysql-bin.000016 |
 
| binlog_snapshot_position                 | 245              |
 
| sphinx_error                             |                  |
 
| sphinx_time                              |                  |
 
| sphinx_total                             |                  |
 
| sphinx_total_found                       |                  |
 
| sphinx_word_count                        |                  |
 
| sphinx_words                             |                  |
 
+------------------------------------------+------------------+
 
415 rows in set (0.00 sec)

I believe that we should have or :

  • Capital letter as good practice for 1st caracter
  • Automatic lower(variable_name) when doing show global status
  • Case-Unsensitive sorting for show global status

Regards,
Joffrey

 Comments   
Comment by Elena Stepanova [ 2012-11-27 ]

Hi Kristian,

Could you please take a look at least at the binlog* part?
It indeed doesn't look too good, especially since we have some Binlog* status variables as well. I'm guessing binlog* ones are somehow unusual (e.g. I don't see them among status_vars[] in mysqld.cc), but the question is whether it has to be this way.

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