[MDEV-5236] Status variables are not all listed alphabetically Created: 2013-11-04  Updated: 2019-10-07  Resolved: 2013-11-12

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.4, 5.5.33a
Fix Version/s: 5.5.34

Type: Bug Priority: Trivial
Reporter: Ian Gilfillan Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7756 Status variables not all alphabetical Open

 Description   

The status variables are mostly, but not entirely, listed alphabetically.

For example:
SHOW STATUS LIKE 'b%';

...

Binlog_commits 5
Binlog_group_commits 5
Binlog_snapshot_file mariadb-bin.000166
Binlog_snapshot_position 369
Binlog_bytes_written 0
Binlog_cache_disk_use 0

...

Variables listed in sql/mysqld.cc are alphabetical, but the variables added elsewhere appear in a block before.

A similar, but unrelated, error occurs with the C's:
SHOW STATUS LIKE 'c%';

Com_admin_commands 0
Com_assign_to_keycache 0
Com_alter_db 0

...

Here, Com_assign... appears too early because it is not listed alphabetically in mysqld.cc



 Comments   
Comment by Ian Gilfillan [ 2013-11-05 ]

The bug report is not a complete list of everything that isn't alphabetical, but I will report more here as I come across them:

Innodb_num_open_files, Innodb_truncated_status_writes and Innodb_available_undo_logs all appear out of order at the end of the I's

Comment by Ian Gilfillan [ 2013-11-19 ]

This is not yet entirely fixed in 10.0.6. The C's are correct, but not the issues reported above with the B's and the I's

Comment by Sergei Golubchik [ 2013-11-19 ]

Yes, the fix for Binlog* variables is too complex to be worth the troubles. I'll sort Innodb's variables, though.

Generated at Thu Feb 08 07:02:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.