For a full list of server options, system variables and status variables, see this page.
Most status variables are described on this page, but some are described elsewhere:
Use the SHOW STATUS statement to view status variables. This information also can be obtained using the mariadb-admin extended-status command, or by querying the Information Schema GLOBAL_STATUS and SESSION_STATUS tables.
Issuing a FLUSH STATUS will reset many status variables to zero.
List of Server Status VariablesDescription: Number of aborted client connections. This can be due to the client not calling mysql_close() before exiting, the client sleeping without issuing a request to the server for more seconds than specified by wait_timeout or interactive_timeout, or by the client program ending in the midst of transferring data. The global value can be flushed by FLUSH STATUS.
Description: Number of failed server connection attempts. This can be due to a client using an incorrect password, a client not having privileges to connect to a database, a connection packet not containing the correct information, or if it takes more than connect_timeout seconds to get a connect packet. The global value can be flushed by FLUSH STATUS.
Description: Number of connection attempts that were aborted prior to authentication (regardless of whether or not an error occured).
Description: Number of database permissions granted (rows in the mysql.db table).
Description: Number of function permissions granted (rows in the mysql.procs_priv table with a routine type of FUNCTION).
Description: Number of procedure permissions granted (rows in the mysql.procs_priv table with a routine type of PROCEDURE).
Description: Cumulative time in seconds of activity on connections. Part of User Statistics. Requires the userstat system variable to be set in order to be recorded.
Description: Total bytes received from all clients.
Description: Total bytes sent to all clients.
Description: Number of admin commands executed. These include table dumps, change users, binary log dumps, shutdowns, pings and debugs.
Description: Number of ALTER TABLESPACE commands executed (unsupported by MariaDB).
Description: Number of ALTER USER commands executed.
Description: Number of ANALYZE commands executed.
Description: Number of assign to keycache commands executed.
Description: Removed in MariaDB 5.5. In older versions, Com_backup_table contains the number of BACKUP TABLE commands executed.
Description: Number of BINLOG commands executed.
Description: Number of CALL procedure_name statements executed.
Description: Number of USE database_name commands executed.
Description: Number of COMMIT commands executed. Differs from Handler_commit, which counts internal commit statements.
Description: Number of compund sql statements.
Description: Number of CREATE EVENT commands executed. Differs from Executed_events in that it is incremented when the CREATE EVENT is run, and not when the event executes.
Com_create_temporary_table
Description: Number of CREATE UDF commands executed.
Description: Number of DEALLOCATE commands executed.
Description: Number of DELETE commands executed. Differs from Handler_delete, which counts the number of times rows have been deleted from tables.
Description: Number of multi-table DELETE commands executed.
Description: Number of DO commands executed.
Description: Number of DROP EVENT commands executed.
Description: Number of DROP INDEX commands executed.
Description: Number of DROP ROLE commands executed.
Description: Number of DROP TABLE commands executed.
Description: Number of DROP USER commands executed.
Description: Number of DROP VIEW commands executed.
Description: Number of queries to the server that do not produce SQL queries. An SQL query simply returning no results does not increment Com_empty_query - see Empty_queries instead. An example of an empty query sent to the server is mariadb --comments -e '-- sql comment'
Description: Number of EXECUTE statements executed.
Description: Number of FLUSH commands executed. This differs from Flush_commands, which also counts internal server flush requests.
Description: Number of GRANT commands executed.
Description: Number of GRANT role commands executed.
Description: Number of HANDLER table_name CLOSE commands executed.
Description: Number of HANDLER table_name OPEN commands executed.
Description: Number of HANDLER table_name READ commands executed.
Description: Number of HELP commands executed.
Description: Number of INSERT commands executed.
Description: Number of KILL commands executed.
Description: Number of LOAD commands executed.
Description: Number of [lock-tables|LOCK TABLES]] commands executed.
Description: Number of OPTIMIZE commands executed.
Description: Number of PREPARE statements executed.
Description: Number of PURGE commands executed.
Description: Number of REPLACE commands executed.
Description: Number of RESET commands executed.
Description: Number of RESIGNAL commands executed.
Description: Removed in MariaDB 5.5. In older versions, Com_restore_table contains the number of RESTORE TABLE commands executed.
Description: Number of REVOKE commands executed.
Description: Number of REVOKE ALL commands executed.
Description: Number of REVOKE role commands executed.
Description: Number of ROLLBACK commands executed. Differs from Handler_rollback, which is the number of transaction rollback requests given to a storage engine.
Com_rollback_to_savepoint
Description: Number of SAVEPOINT commands executed. Differs from Handler_savepoint, which is the number of transaction savepoint creation requests.
Description: Number of SELECT commands executed. Also includes queries that make use of the query cache.
Description: Number of SET OPTION commands executed.
Description: Number of SIGNAL statements executed.
Com_show_client_statistics
Com_show_create_package_body
Description: Number of SHOW COLUMNS or SHOW FIELDS commands executed.
Description: Number of SHOW INDEX or SHOW KEYS commands executed.
Com_show_index_statistics
Com_show_package_body_status
Com_show_procedure_status
Com_show_table_statistics
Description: Number of SHUTDOWN commands executed.
Description: Number of prepared statements where the data of a prepared statement which was accumulated in chunks by sending long data has been reset.
Description: Number of prepared statements where the parameter data has been sent in chunks (long data).
Description: Number of TRUNCATE commands executed.
Description: Number of UPDATE commands executed.
Description: Number of multi-table UPDATE commands executed.
Description: Number of XA statements committed.
Description: Number of XA statements ended.
Description: Number of XA statements prepared.
Description: Number of XA RECOVER statements executed.
Description: Number of XA statements rolled back.
Description: Number of XA statements started.
Description: Whether client-server traffic is compressed.
Description: Number of errors that occurred during calls to accept() on the listening port. The global value can be flushed by FLUSH STATUS.
Connection_errors_internal
Description: Number of refused connections due to internal server errors, for example out of memory errors, or failed thread starts. The global value can be flushed by FLUSH STATUS.
Connection_errors_max_connections
Description: Number of refused connections due to the max_connections limit being reached. The global value can be flushed by FLUSH STATUS.
Connection_errors_peer_address
Description: Number of errors while searching for the connecting client IP address. The global value can be flushed by FLUSH STATUS.
Description: Number of errors during calls to select() or poll() on the listening port. The client would not necessarily have been rejected in these cases. The global value can be flushed by FLUSH STATUS.
Connection_errors_tcpwrap
Description: Number of connections the libwrap library refused. The global value can be flushed by FLUSH STATUS.
Description: Number of connection attempts (both successful and unsuccessful)
Description: Total CPU time used. Part of User Statistics. Requires the userstat system variable to be set in order to be recorded.
Description: Number of on-disk temporary tables created.
Description: Number of temporary files created. The global value can be flushed by FLUSH STATUS.
Description: Number of in-memory temporary tables created.
Description: Number of DELETE s that required a full table scan.
Description: Number of queries returning no results. Note this is not the same as Com_empty_query.
Description: Number of times events created with CREATE EVENT have executed. This differs from Com_create_event in that it is only incremented when the event has run, not when it executes.
Description: Number of times triggers created with CREATE TRIGGER have executed. This differs from Com_create_trigger in that it is only incremented when the trigger has run, not when it executes.
Feature_application_time_periods
Description: Number of times a table created with periods has been opened.
Feature_custom_aggregate_functions
Description: Number of times a table with a any of the geometry columns was opened.
Feature_invisible_columns
Description: Number of invisible columns in all opened tables.
Description: Number of times the @@lc_messages variable was assigned into.
Description: Number of subqueries (excluding subqueries in the FROM clause) used.
Feature_system_versioning
Description: Number of times system versioning functionality has been used (opening a table WITH SYSTEM VERSIONING).
Description: Number of times an explicit timezone (excluding UTC and SYSTEM) was specified.
Description: Number of triggers loaded.
Description: Number of FLUSH statements executed, as well as due to internal server flush requests. This differs from Com_flush, which simply counts FLUSH statements, not internal server flush operations.
Description: Number of internal COMMIT requests. Differs from Com_commit, which counts the number of COMMIT statements executed.
Description: Number of times rows have been deleted from tables. Differs from Com_delete, which counts DELETE statements.
Description: Discovery is when the server asks the NDBCLUSTER storage engine if it knows about a table with a given name. Handler_discover indicates the number of times that tables have been discovered in this way.
Description: Incremented for each call to the external_lock() function, which generally occurs at the beginning and end of access to a table instance.
Description: Number of times key buffer was refilled (not counting the initial fill). A non-zero value indicates there wasn't enough memory to do key sort-and-sweep passes in one go. See Multi Range Read optimization.
Handler_mrr_rowid_refills
Description: Number of times rowid buffer was refilled (not counting the initial fill). A non-zero value indicates there wasn't enough memory to do rowid sort-and-sweep passes in one go. See Multi Range Read optimization.
Description: Number of two-phase commit prepares.
Description: Number of requests to read the first row from an index. A high value indicates many full index scans, e.g. SELECT a FROM table_name where a is an indexed column.
Description: Number of row read requests based on an index value. A high value indicates indexes are regularly being used, which is usually positive.
Description: Number of requests to read the last row from an index. ORDER BY DESC results in a last-key request followed by several previous-key requests.
Description: Number of requests to read the next row from an index (in order). Increments when doing an index scan or querying an index column with a range constraint.
Description: Number of requests to read the previous row from an index (in order). Mostly used with ORDER BY DESC.
Description: Number of read retrys triggered by semi_consistent_read (InnoDB feature).
Description: Number of requests to read a row based on its position. If this value is high, you may not be using joins that don't use indexes properly, or be doing many full table scans.
Description: Number of requests to delete a row based on its position.
Description: Number of requests to read the next row. A large number of these may indicate many table scans and improperly used indexes.
Description: Number of transaction rollback requests given to a storage engine. Differs from Com_rollback, which is the number of ROLLBACK commands executed.
Description: Number of transaction savepoint creation requests. Differs from Com_savepoint which is the number of SAVEPOINT commands executed.
Handler_savepoint_rollback
Description: Number of requests to rollback to a transaction savepoint.
Description: Number of requests to delete a row in a temporary table.
Description: Number of requests to update a row to a temporary table.
Description: Number of requests to write a row to a temporary table.
Description: Number of requests to write a row to a table. Since MariaDB 5.3, this no longer counts temporary tables - see Handler_tmp_write.
Description: Number of key cache blocks which have been modified but not flushed to disk.
Description: Number of unused key cache blocks.
Description: Max number of key cache blocks which have been used simultaneously.
Description: Number of key cache blocks in the warm list.
Description: Number of requests to write a block to the key cache.
Description: Number of key cache block write requests
Description: The most recent query optimizer query cost calculation. Can not be calculated for complex queries, such as subqueries or UNION. It will be set to 0 for complex queries.
Description: When the Maria storage engine was renamed Aria, the Maria variables existing at the time were renamed at the same time. See Aria Server Status Variables.
Description: The maximum memory allocation used by the current connection.
Max_statement_time_exceeded
Description: Max number of connections ever open at the same time. The global value can be flushed by FLUSH STATUS.
Max_used_connections_time
Description: Global or per-connection memory usage, in bytes. This includes all per-connection memory allocations, but excludes global allocations such as the key_buffer, innodb_buffer_pool etc.
Description: Amount of memory that was used when the server started to service the user connections.
Description: Number of regular files currently opened by the server. Does not include sockets or pipes, or storage engines using internal functions.
Description: Number of currently opened streams, usually log files.
Description: Number of currently cached .frm files.
Description: Number of currently opened tables, excluding temporary tables.
Description: Number of files the server has opened.
Description: Number of shared libraries that the server has opened to load plugins.
Description: Number of .frm files that have been cached.
Description: Number of tables the server has opened.
Description: Number of views the server has opened.
Description: Current number of prepared statements.
Description: Number of pruning operations performed to remove old results to make space for new results in the query cache. The global value can be flushed by FLUSH STATUS.
Description: Number of queries that are uncacheable by the query cache, or use SQL_NO_CACHE. The global value can be flushed by FLUSH STATUS.
Description: Number of queries currently cached by the query cache.
Description: Number of statements executed by the server, excluding COM_PING and COM_STATISTICS. Differs from Questions in that it also counts statements executed within stored programs.
Description: Cumulative time in seconds, with microsecond precision, of running queries.
Description: Number of statements executed by the server, excluding COM_PING, COM_STATISTICS, COM_STMT_PREPARE, COM_STMT_CLOSE, and COM_STMT_RESET statements. Differs from Queries in that it doesn't count statements executed within stored programs.
Resultset_metadata_skipped
Description: Number of times sending the metadata has been skipped. Metadata is not resent if metadata does not change between prepare and execute of prepared statement, or between executes.
Description: Number of requests to read a row (excluding temporary tables).
Description: Number of requests to read a row in a temporary table.
Description: Number of joins which did not use an index. If not zero, you may need to check table indexes.
Description: Number of joins which used a range search of the first table.
Description: Number of joins which used a range on the first table.
Description: Number of joins without keys that check for key usage after each row. If not zero, you may need to check table indexes.
Description: Number of joins which used a full scan of the first table.
Description: Number of queries which took longer than long_query_time to run. The slow query log does not need to be active for this to be recorded.
Description: Number of merge passes performed by the sort algorithm. If too high, you may need to look at improving your query indexes, or increasing the sort_buffer_size.
Sort_priority_queue_sorts
Description: Number of sorts which used a range.
Description: Number of rows sorted.
Description: Number of sorts which used a full table scan.
Description: Number of times my_sync() has been called, or the number of times the server has had to force data to disk. Covers the binary log, .frm creation (if these operations are configured to sync) and some storage engines (Archive,CSV, Aria), but not XtraDB/InnoDB).
Description: Number of table locks which were completed immediately. The global value can be flushed by FLUSH STATUS.
Description: Number of table locks which had to wait. Indicates table lock contention. The global value can be flushed by FLUSH STATUS.
Table_open_cache_active_instances
Description: Number of active instances for open tables cache lookups.
Description: Number of hits for open tables cache lookups.
Description: Number of misses for open tables cache lookups.
Table_open_cache_overflows
Description: Number of overflows for open tables cache lookups.
Description: Number of threads cached in the thread cache. This value will be zero if the thread pool is in use.
Description: Number of clients connected to the server. See Handling Too Many Connections. The Threads_connected name is inaccurate when the thread pool is in use, since each client connection does not correspond to a dedicated thread in that case.
Description: Number of threads created to respond to client connections. If too large, look at increasing thread_cache_size.
Description: Number of client connections that are actively running a command, and not just sleeping while waiting to receive the next command to execute. Some internal system threads also count towards this status variable if they would show up in the output of the SHOW PROCESSLIST statement.
In MariaDB 10.3.2 and before, a global counter was updated each time a client connection dispatched a command. In these versions, the global and session status variable are always the same value.
In MariaDB 10.3.3 and later, the global counter has been removed as a performance improvement. Instead, when the global status variable is queried, it is calculated dynamically by essentially adding up all the running client connections as they would appear in SHOW PROCESSLIST output. A client connection is only considered to be running if its thread COMMAND value is not equal to Sleep. When the session status variable is queried, it always returns 1.
Description: Number of updates that required a full table scan.
Description: Number of seconds the server has been running.
Uptime_since_flush_status
This page is licensed: CC BY-SA / Gnu FDL
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4