[MDEV-5790] SHOW GLOBAL STATUS LIKE does not show the correct list of variables when using "_" Created: 2014-03-04  Updated: 2014-04-10  Resolved: 2014-04-10

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.7-galera
Fix Version/s: 10.0.10-galera

Type: Bug Priority: Critical
Reporter: Ivan Zoratti (Inactive) Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 6.5



 Description   

When I filter the list of variables in the SHOW STATUS command with a LIKE that contains and underscore, I do not see all the variables that match the criteria.

It works fine in previous versions.

Here is how to reproduce the issue:

MariaDB [(none)]> show global status like 'wsrep%';
-----------------------------------------------------------------------------------+

Variable_name Value

-----------------------------------------------------------------------------------+

Wsrep_local_state_uuid 4122599e-a20f-11e3-8273-a25a551b0af0
Wsrep_protocol_version 5
Wsrep_last_committed 3
Wsrep_replicated 1
Wsrep_replicated_bytes 197
Wsrep_repl_keys 1
Wsrep_repl_keys_bytes 31
Wsrep_repl_data_bytes 102
Wsrep_repl_other_bytes 0
Wsrep_received 6
Wsrep_received_bytes 1008
Wsrep_local_commits 0
Wsrep_local_cert_failures 0
Wsrep_local_replays 0
Wsrep_local_send_queue 0
Wsrep_local_send_queue_avg 0.000000
Wsrep_local_recv_queue 0
Wsrep_local_recv_queue_avg 0.166667
Wsrep_local_cached_downto 1
Wsrep_flow_control_paused_ns 0
Wsrep_flow_control_paused 0.000000
Wsrep_flow_control_sent 0
Wsrep_flow_control_recv 0
Wsrep_cert_deps_distance 1.000000
Wsrep_apply_oooe 0.000000
Wsrep_apply_oool 0.000000
Wsrep_apply_window 1.000000
Wsrep_commit_oooe 0.000000
Wsrep_commit_oool 0.000000
Wsrep_commit_window 1.000000
Wsrep_local_state 4
Wsrep_local_state_comment Synced
Wsrep_cert_index_size 3
Wsrep_causal_reads 0
Wsrep_incoming_addresses 192.168.0.21:3306,192.168.0.22:3306,192.168.0.23:3306
Wsrep_cluster_conf_id 3
Wsrep_cluster_size 3
Wsrep_cluster_state_uuid 4122599e-a20f-11e3-8273-a25a551b0af0
Wsrep_cluster_status Primary
Wsrep_connected ON
Wsrep_local_bf_aborts 0
Wsrep_local_index 0
Wsrep_provider_name Galera
Wsrep_provider_vendor Codership Oy <info@codership.com>
Wsrep_provider_version 25.3.2(r170)
Wsrep_ready ON

-----------------------------------------------------------------------------------+
46 rows in set (0.00 sec)

MariaDB [(none)]> show global status like 'wsrep_%';
--------------------------------------------------------------+

Variable_name Value

--------------------------------------------------------------+

Wsrep_cluster_conf_id 3
Wsrep_cluster_size 3
Wsrep_cluster_state_uuid 4122599e-a20f-11e3-8273-a25a551b0af0
Wsrep_cluster_status Primary
Wsrep_connected ON
Wsrep_local_bf_aborts 0
Wsrep_local_index 0
Wsrep_provider_name Galera
Wsrep_provider_vendor Codership Oy <info@codership.com>
Wsrep_provider_version 25.3.2(r170)
Wsrep_ready ON

--------------------------------------------------------------+
11 rows in set (0.00 sec)

MariaDB [(none)]> show global status like 'wsrep_local_state_comment';
Empty set (0.00 sec)



 Comments   
Comment by Nirbhay Choubey (Inactive) [ 2014-03-05 ]

Fix pushed to maria-10.0-galera.

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