1 of 100

Information Schema

Query information_schema.tables in MariaDB Server. This system table provides metadata about all tables in the databases, including their names, types, storage engines, and other crucial properties.

TIME_MS column in INFORMATION_SCHEMA.PROCESSLIST

The TIME_MS column in the INFORMATION_SCHEMA.PROCESSLIST table displays the time a thread has been in its current state in milliseconds, offering higher precision than the standard TIME column.

In MariaDB, an extra column TIME_MS was added to the INFORMATION_SCHEMA.PROCESSLIST table. This column shows the same information as the column 'TIME', but in units of milliseconds with microsecond precision (the unit and precision of theTIME column is one second).

For details about microseconds support in MariaDB, see microseconds in MariaDB.

The value displayed in the TIME andTIME_MS columns is the period of time that the given thread has been in its current state. Thus, it can be used to check for example how long a thread has been executing the current query, or for how long it has been idle.

SELECT id, TIME, time_ms, command, state FROM
   information_schema.processlist, (SELECT sleep(2)) t;
+----+------+----------+---------+-----------+
| id | time | time_ms  | command | state     |
+----+------+----------+---------+-----------+
| 37 |    2 | 2000.493 | Query   | executing |
+----+------+----------+---------+-----------+

Note that as a difference to MySQL, in MariaDB the TIME column (and also the TIME_MS column) are not affected by any setting of . This means that it can be reliably used also for threads that change @TIMESTAMP (such as the SQL thread). See also .

As a consequence of this, the TIME column ofSHOW FULL PROCESSLIST andINFORMATION_SCHEMA.PROCESSLIST cannot be used to determine if a slave is lagging behind. For this, use instead theSeconds_Behind_Master column in the output of .

The addition of the TIME_MS column is based on the microsec_process patch, developed by .

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema Tables

Query information_schema.tables in MariaDB Server. These system tables provides metadata about all tables in the databases, including their names, types, storage engines, and other crucial properties.

Information Schema ALL_PLUGINS Table

The Information Schema ALL_PLUGINS table contains information about server plugins, whether installed or not, providing a superset of SHOW PLUGINS SONAME.

Description

The Information Schema ALL_PLUGINS table contains information about server plugins, whether installed or not.

It contains the following columns:

Column

Description

It provides a superset of the information shown by the statement, as well as the table. For specific information about storage engines (a particular type of plugin), see the and the statement.

The table is not a standard Information Schema table, and is a MariaDB extension.

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema APPLICABLE_ROLES Table

The Information Schema APPLICABLE_ROLES table shows the role authorizations that the current user may use, detailing grantable and default status.

The APPLICABLE_ROLES table shows the that the current user may use.

It contains the following columns:

Column

Description

Information Schema CATALOG Table

The Information Schema CATALOG table stores information about catalogs on the server, including default character sets and collations.

This table is available as of MariaDB 12.0.

The Information Schema CATALOG table stores information about catalogs on the server.

It contains the following columns:

Column

Description

Example

Information Schema CHARACTER_SETS Table

The Information Schema CHARACTER_SETS table contains a list of supported character sets, their default collations, and maximum lengths.

The Information Schema CHARACTER_SETS table contains a list of supported character sets, their default collations and maximum lengths.

It contains the following columns:

Column

Description

CHARACTER_SET_NAME

Name of the character set.

DEFAULT_COLLATE_NAME

Default collation used.

DESCRIPTION

The statement returns the same results (although in a different order), and both can be refined in the same way. For example, the following two statements return the same results:

and

See for details on specifying the character set at the server, database, table and column levels, and for a full list of supported characters sets and collations.

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema COLLATION_CHARACTER_SET_APPLICABILITY Table

The Information Schema COLLATION_CHARACTER_SET_APPLICABILITY table maps which character sets are associated with which collations.

The Information Schema COLLATION_CHARACTER_SET_APPLICABILITY table shows which character sets are associated with which collations.

It contains the following columns:

Column

Description

COLLATION_NAME

Collation name.

CHARACTER_SET_NAME

Name of the associated character set.

FULL_COLLATION_NAME

The table is table of the base COLLATION_NAMES in the same way that table is table of the base CHARACTER_SET_NAMES. The COLLATION_CHARACTER_SET_APPLICABILITY table is the mapping between collations and character sets.

When joining the table with its field TABLE_COLLATIONS, this should be joined to FULL_COLLATION_NAME in the COLLATION_CHARACTER_SET_APPLICABILITY table.

See for details on specifying the character set at the server, database, table and column levels.

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema COLUMN_PRIVILEGES Table

The Information Schema COLUMN_PRIVILEGES table contains column privilege information derived from the mysql.columns_priv grant table.

The Information Schema COLUMN_PRIVILEGES table contains column privilege information derived from the mysql.columns_priv grant table.

It has the following columns:

Column

Description

GRANTEE

In the format user_name@host_name.

TABLE_CATALOG

Always def.

TABLE_SCHEMA

Similar information can be accessed with the and statements. See the statement for details about privileges.

This information is also stored in the table, in the mysql system database.

For a description of the privileges that are shown in this table, see .

Example

In the following example, no column-level privilege has been explicitly assigned:

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema DISKS Table

The Information Schema DISKS table, created by the DISKS plugin, displays metadata such as total and available space for disks on the system.

The plugin only works on Linux.

Description

The DISKS table is created when the plugin is enabled, and shows metadata about disks on the system.

This plugin requires the .

This plugin does not check . When it is enabled, any user can query the INFORMATION_SCHEMA.DISKS table and see all the information it provides.

The table contains the following columns:

Column

Description

Note that as the amount of space available to root (OS user) may be more that what is available to non-root users, 'available' + 'used' may be less than 'total'.

All paths to which a particular disk has been mounted are reported. The rationale is that someone might want to take different action e.g. depending on which disk is relevant for a particular path. This leads to the same disk being reported multiple times.

Example

Information Schema ENABLED_ROLES Table

The Information Schema ENABLED_ROLES table lists all roles that are currently enabled for the current session, including nested roles.

The Information Schema ENABLED_ROLES table shows the enabled roles for the current session.

It contains the following column:

Column

Description

ROLE_NAME

The enabled role name, or NULL.

This table lists all roles that are currently enabled, one role per row — the current role, roles granted to the current role, roles granted to these roles and so on. If no role is set, the row contains a NULL value.

The roles that the current user can enable are listed in the Information Schema table.

Examples

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema GLOBAL_STATUS and SESSION_STATUS Tables

The GLOBAL_STATUS and SESSION_STATUS tables store the global and session values of server status variables, respectively.

The GLOBAL_STATUS and SESSION_STATUS tables store a record of all and their global and session values respectively. This is the same information as displayed by the commands SHOW GLOBAL STATUS and SHOW SESSION STATUS.

They contain the following columns:

Column

Description

Information Schema GLOBAL_VARIABLES and SESSION_VARIABLES Tables

The GLOBAL_VARIABLES and SESSION_VARIABLES tables store the global and session values of all system variables, respectively.

The Information Schema GLOBAL_VARIABLES and SESSION_VARIABLES tables stores a record of all system variables and their global and session values respectively. This is the same information as displayed by the SHOW VARIABLES commands SHOW GLOBAL VARIABLES and SHOW SESSION VARIABLES.

It contains the following columns:

Column

Description

VARIABLE_NAME

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema INDEX_STATISTICS Table

The Information Schema INDEX_STATISTICS table provides statistics on index usage, helping to identify unused indexes and optimize performance.

The INDEX_STATISTICS table shows statistics on index usage and makes it possible to do such things as locating unused indexes and generating the commands to remove them.

This is part of the feature, which is not enabled by default.

It contains the following columns:

Field

Type

Notes

Information Schema KEY_CACHES Table

The Information Schema KEY_CACHES table displays statistics about the segmented key cache, including block usage and read/write requests.

The Information Schema KEY_CACHES table shows statistics about the segmented key cache.

It contains the following columns:

Column Name

Description

KEY_CACHE_NAME

The name of the key cache

SEGMENTS

total number of segments (set to NULL for regular key caches)

SEGMENT_NUMBER

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema KEY_PERIOD_USAGE Table

The Information Schema KEY_PERIOD_USAGE table describes how keys reference application-time periods, detailing constraints involving those periods.

This table is available as of MariaDB 11.4.

The KEY_PERIOD_USAGE table shows information about .

It contains the following columns:

Column

Description

Information Schema LOCALES Table

The Information Schema LOCALES table lists all compiled-in locales available to the server, providing their IDs, names, and descriptions.

Description

The Information Schema LOCALES table contains a list of all compiled-in locales. It is only available if the LOCALES plugin has been installed.

It contains the following columns:

Column

Description

The table is not a standard Information Schema table, and is a MariaDB extension.

The statement returns a subset of the information.

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema MROONGA_STATS Table

The Information Schema MROONGA_STATS table provides statistical information specific to the Mroonga full-text search storage engine.

The MROONGA_STATS table only exists if the storage engine is installed, and contains information about its activities.

Column

Description

Information Schema OPTIMIZER_TRACE Table

The Information Schema OPTIMIZER_TRACE table contains details about the optimizer's decision-making process for the last executed query.

Description

The OPTIMIZER_TRACE table contains information.

It contains the following columns:

Column

Description

Information Schema PERIODS Table

The Information Schema PERIODS table provides information about Application-Time Periods, detailing the start and end columns for system versioning.

This table is available as of MariaDB 11.4.

The PERIODS table provides information about .

It contains the following columns:

Column

Description

Information Schema PROFILING Table

The Information Schema PROFILING table provides statement resource usage details, such as CPU time and block operations, when profiling is enabled.

The Information Schema PROFILING table contains information about statement resource usage. Profiling information is only recorded if the profiling session variable is set to 1.

It contains the following columns:

Column Name

Description

QUERY_ID

Query_ID.

SEQ

It contains similar information to the and statements.

Profiling is enabled per session. When a session ends, its profiling information is lost.

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema QUERY_RESPONSE_TIME Table

The Information Schema QUERY_RESPONSE_TIME table displays the distribution of query execution times, helping to identify performance bottlenecks.

Description

The Information Schema QUERY_RESPONSE_TIME table contains information about queries that take a long time to execute . It is only available if the QUERY_RESPONSE_TIME plugin has been installed.

It contains the following columns:

Column

Description

See plugin for a full description.

The table is not a standard Information Schema table, and is a MariaDB extension.

is available as an alternative for retrieving the data.

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema REFERENTIAL_CONSTRAINTS Table

The Information Schema REFERENTIAL_CONSTRAINTS table contains metadata about foreign keys, including update and delete rules.

The REFERENTIAL_CONSTRAINTS table contains information about . The single columns are listed in the table.

It has the following columns:

Column

Description

Information Schema SCHEMA_PRIVILEGES Table

The Information Schema SCHEMA_PRIVILEGES table contains information about database-level privileges granted to accounts.

The Information Schema SCHEMA_PRIVILEGES table contains information about database privileges.

It contains the following columns:

Column

Description

GRANTEE

Account granted the privilege in the format user_name@host_name.

TABLE_CATALOG

Always def

TABLE_SCHEMA

The same information in a different format can be found in the table.

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema SLAVE_STATUS Table

The Information Schema SLAVE_STATUS table displays status information for the replication slave threads, similar to SHOW SLAVE STATUS.

This table is available as of MariaDB .

The SLAVE_STATUS table contains replica status information, similar to .

See for column descriptions.

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema SPIDER_ALLOC_MEM Table

The Information Schema SPIDER_ALLOC_MEM table tracks memory allocation for the Spider storage engine, aiding in resource monitoring.

The SPIDER_ALLOC_MEM table is installed along with the storage engine. It shows information about Spider's memory usage.

It contains the following columns:

Column

Description

Information Schema TABLE_CONSTRAINTS Table

The Information Schema TABLE_CONSTRAINTS table describes constraints on tables, such as PRIMARY KEY, UNIQUE, and FOREIGN KEY constraints.

The Information Schema TABLE_CONSTRAINTS table contains information about tables that have constraints.

It has the following columns:

Column

Description

CONSTRAINT_CATALOG

Always def.

CONSTRAINT_SCHEMA

Database name containing the constraint.

CONSTRAINT_NAME

The table has more information about foreign keys.

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema TABLE_PRIVILEGES Table

The Information Schema TABLE_PRIVILEGES table lists privileges granted specifically at the table level.

The Information Schema TABLE_PRIVILEGES table contains table privilege information derived from the mysql.tables_priv grant table.

It has the following columns:

Column

Description

GRANTEE

In the format user_name@host_name.

TABLE_CATALOG

Always def.

TABLE_SCHEMA

Similar information can be accessed with the statement. See the article for more about privileges.

The table only shows privileges granted on the table level. This differs from the Sys Schema , which shows all privileges, broken down by table.

For a description of the privileges that are shown in this table, see .

Information Schema TABLE_STATISTICS Table

The Information Schema TABLE_STATISTICS table provides usage statistics for tables, such as the number of rows read or changed.

The Information Schema TABLE_STATISTICS table shows statistics on table usage.

This is part of the User Statistics feature, which is not enabled by default.

It contains the following columns:

Field

Type

Notes

TABLE_SCHEMA

varchar(192)

The schema (database) name.

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema TABLESPACES Table

The Information Schema TABLESPACES table provides information about active tablespaces, specifically for the InnoDB storage engine.

The Information Schema TABLESPACES table contains information about active tablespaces..

The table is a MariaDB and MySQL extension, and does not include information about InnoDB tablespaces.

Column

Description

TABLESPACE_NAME

ENGINE

TABLESPACE_TYPE

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema THREAD_POOL_GROUPS Table

The Information Schema THREAD_POOL_GROUPS table provides details about the thread groups in the thread pool, including active thread counts.

This table is available as of MariaDB 10.5.

The table provides information about groups, and contains the following columns:

Column

Description

Information Schema USER_PRIVILEGES Table

The Information Schema USER_PRIVILEGES table lists global privileges granted to user accounts, derived from the mysql.user table.

The Information Schema USER_PRIVILEGES table contains global user privilege information derived from the mysql.global_priv grant table.

It contains the following columns:

Column

Description

GRANTEE

In the format user_name@host_name.

TABLE_CATALOG

Always def.

PRIVILEGE_TYPE

The database, table and column privileges returned here are the ones granted on all databases and tables, and by implication all columns.

Similar information can be accessed with the statement. See the article for more about privileges.

This information is also stored in the table, in the mysql system database.

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema USERS Table

The Information Schema USERS table lists user accounts, including whether they are global or local, and details about their password expiration.

This table is available from .

The USERS table contains information about users, , and the limits set by . Unprivileged users can access their own data, which is different to what provides.

It contains the following columns:

Column

Description

Information Schema WSREP_CERT_KEYS

The Information Schema WSREP_CERT_KEYS table displays the certification keys for transactions currently being processed by the Galera Cluster.

This table is used in MariaDB Galera Cluster.

This table is available as of MariaDB Enterprise Server 11.8.

The Wsrep certification keys, the primary keys of changed rows, are collected into a write set for Galera Cluster's certification-based replication. The write set is used to ensure data consistency by detecting conflicting transactions before they commit. The WSREP_CERT_INFO plugin exposes wsrep certification keys in two information schema tables: WSREP_CERT_KEYS (this table), and WSREP_CERT_KEYS_HISTORY.

There are several key types.

Exclusive

The Exclusive key type is used when a transaction inserts, updates, or deletes a row. Example:

Reference

The Reference key type is used when a FOREIGN KEY constraint is defined with referenced table key tpe set as REFERENCE. In the example, 706172656E74 is a hexadecimal value for 'parent'. Example:

Update

The Update key type is used when a transaction updates a row and wsrep_protocol_version is greater than 4. Otherwise, the Exclusive key type is used. Example:

Shared

This key type is used when a referenced table update happens, and wsrep_protocol_version is smaller than 4.

Information Schema WSREP_CERT_KEYS_HISTORY

The Information Schema WSREP_CERT_KEYS_HISTORY table logs a history of certification keys for recently processed Galera transactions.

This table is used in .

This table is available as of MariaDB Enterprise Server 11.8.

This table contains certification key information history for Galera threads. See the documentation for details.

Information Schema WSREP_CONNECTIONS

The Information Schema WSREP_CONNECTIONS table shows active connections to the Galera Cluster, primarily used for debugging cluster membership.

This table is used in MariaDB Galera Cluster.

This table is available as of MariaDB Enterprise Server 11.8.

This table contains active Galera connections on queried nodes in the cluster. Example output:

MariaDB [(none)]> SELECT * FROM information_schema.wsrep_connections;
+-----------------+-------------------+-----------------+-----------------+------------------------+---------------------------------------------------+------------------------------------------------------+---------------------+
| connection_id   | connection_scheme | local_address   | remote_address  | cipher                 | certificate_subject                               | certificate_issuer                                   | certificate_version |
+-----------------+-------------------+-----------------+-----------------+------------------------+---------------------------------------------------+------------------------------------------------------+---------------------+
| 136018124822096 | ssl               | 127.0.0.1:19033 | 127.0.0.1:59010 | TLS_AES_256_GCM_SHA384 | /C=FI/ST=Helsinki/L=Helsinki/O=Galera/CN=galera.1 | /C=FI/ST=Helsinki/L=Helsinki/O=Galera/CN=galera.root | TLSv1.3             |
| 136018124966656 | ssl               | 127.0.0.1:49650 | 127.0.0.1:19039 | TLS_AES_256_GCM_SHA384 | /C=FI/ST=Helsinki/L=Helsinki/O=Galera/CN=galera.1 | /C=FI/ST=Helsinki/L=Helsinki/O=Galera/CN=galera.root | TLSv1.3             |
+-----------------+-------------------+-----------------+-----------------+------------------------+---------------------------------------------------+------------------------------------------------------+---------------------+
2 rows in set (0.004 sec)

Information Schema WSREP_THD_STATE_HISTORY

The Information Schema WSREP_THD_STATE_HISTORY table maintains a history of thread states for Galera replication, aiding in post-incident analysis.

This table is used in MariaDB Galera Cluster.

This table is available as of MariaDB Enterprise Server 11.8.

This table contains execution state information history for Galera threads. See the WSREP_THD_STATE documentation for details.

Information Schema InnoDB Tables

These system tables provide detailed metadata about InnoDB tables, including their structure, storage, and other crucial properties for analysis.

Information Schema INNODB_BUFFER_POOL_PAGES_INDEX Table

The INNODB_BUFFER_POOL_PAGES_INDEX table provides information about index pages in the buffer pool, specific to the XtraDB engine.

The Information Schema INNODB_BUFFER_POOL_PAGES table is a Percona enhancement, and is only available for XtraDB, not InnoDB (see XtraDB and InnoDB). It contains information about buffer pool index pages.

It has the following columns:

Column

Description

INDEX_ID

Index name

SPACE_ID

Tablespace ID

_{This page is licensed: CC BY-SA / Gnu FDL}

Information Schema INNODB_CMPMEM and INNODB_CMPMEM_RESET Tables

These tables provide status statistics on compressed pages within the buffer pool, useful for analyzing compression efficiency.

The INNODB_CMPMEM and INNODB_CMPMEM_RESET tables contain status information on compressed pages in the buffer pool (see InnoDB COMPRESSED format).

The PROCESS privilege is required to query this table.

These tables contain the following columns:

Column Name

Description

PAGE_SIZE

Compressed page size, in bytes. This value is unique in the table; other values are totals which refer to pages of this size.

These tables can be used to measure the effectiveness of InnoDB table compression. When you have to decide a value for KEY_BLOCK_SIZE, you can create more than one version of the table (one for each candidate value) and run a realistic workload on them. Then, these tables can be used to see how the operations performed with different page sizes.

INNODB_CMPMEM and INNODB_CMPMEM_RESET have the same columns and always contain the same values, but when INNODB_CMPMEM_RESET is queried, the RELOCATION_TIME column from both the tables are cleared. INNODB_CMPMEM_RESET can be used, for example, if a script periodically logs the performances of compression in the last period of time. INNODB_CMPMEM can be used to see the cumulated statistics.

Example

SELECT * FROM information_schema.all_plugins\G *************************** 1. row *************************** PLUGIN_NAME: binlog PLUGIN_VERSION: 1.0 PLUGIN_STATUS: ACTIVE PLUGIN_TYPE: STORAGE ENGINE PLUGIN_TYPE_VERSION: 100314.0 PLUGIN_LIBRARY: NULL PLUGIN_LIBRARY_VERSION: NULL PLUGIN_AUTHOR: MySQL AB PLUGIN_DESCRIPTION: This is a pseudo storage engine to represent the binlog in a transaction PLUGIN_LICENSE: GPL LOAD_OPTION: FORCE PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 2. row *************************** PLUGIN_NAME: mysql_native_password PLUGIN_VERSION: 1.0 PLUGIN_STATUS: ACTIVE PLUGIN_TYPE: AUTHENTICATION PLUGIN_TYPE_VERSION: 2.1 PLUGIN_LIBRARY: NULL PLUGIN_LIBRARY_VERSION: NULL PLUGIN_AUTHOR: R.J.Silk, Sergei Golubchik PLUGIN_DESCRIPTION: Native MySQL authentication PLUGIN_LICENSE: GPL LOAD_OPTION: FORCE PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 3. row *************************** PLUGIN_NAME: mysql_old_password PLUGIN_VERSION: 1.0 PLUGIN_STATUS: ACTIVE PLUGIN_TYPE: AUTHENTICATION PLUGIN_TYPE_VERSION: 2.1 PLUGIN_LIBRARY: NULL PLUGIN_LIBRARY_VERSION: NULL PLUGIN_AUTHOR: R.J.Silk, Sergei Golubchik PLUGIN_DESCRIPTION: Old MySQL-4.0 authentication PLUGIN_LICENSE: GPL LOAD_OPTION: FORCE PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 ... *************************** 104. row *************************** PLUGIN_NAME: WSREP_MEMBERSHIP PLUGIN_VERSION: 1.0 PLUGIN_STATUS: NOT INSTALLED PLUGIN_TYPE: INFORMATION SCHEMA PLUGIN_TYPE_VERSION: 100314.0 PLUGIN_LIBRARY: wsrep_info.so PLUGIN_LIBRARY_VERSION: 1.13 PLUGIN_AUTHOR: Nirbhay Choubey PLUGIN_DESCRIPTION: Information about group members PLUGIN_LICENSE: GPL LOAD_OPTION: OFF PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 105. row *************************** PLUGIN_NAME: WSREP_STATUS PLUGIN_VERSION: 1.0 PLUGIN_STATUS: NOT INSTALLED PLUGIN_TYPE: INFORMATION SCHEMA PLUGIN_TYPE_VERSION: 100314.0 PLUGIN_LIBRARY: wsrep_info.so PLUGIN_LIBRARY_VERSION: 1.13 PLUGIN_AUTHOR: Nirbhay Choubey PLUGIN_DESCRIPTION: Group view information PLUGIN_LICENSE: GPL LOAD_OPTION: OFF PLUGIN_MATURITY: Stable

SELECT * FROM information_schema.LOCALES; +-----+-------+-------------------------------------+-----------------------+---------------------+---------------+--------------+------------------------+ | ID | NAME | DESCRIPTION | MAX_MONTH_NAME_LENGTH | MAX_DAY_NAME_LENGTH | DECIMAL_POINT | THOUSAND_SEP | ERROR_MESSAGE_LANGUAGE | +-----+-------+-------------------------------------+-----------------------+---------------------+---------------+--------------+------------------------+ | 0 | en_US | English - United States | 9 | 9 | . | , | english | | 1 | en_GB | English - United Kingdom | 9 | 9 | . | , | english | | 2 | ja_JP | Japanese - Japan | 3 | 3 | . | , | japanese | | 3 | sv_SE | Swedish - Sweden | 9 | 7 | , | | swedish | | 4 | de_DE | German - Germany | 9 | 10 | , | . | german | | 5 | fr_FR | French - France | 9 | 8 | , | | french | | 6 | ar_AE | Arabic - United Arab Emirates | 6 | 8 | . | , | english | | 7 | ar_BH | Arabic - Bahrain | 6 | 8 | . | , | english | | 8 | ar_JO | Arabic - Jordan | 12 | 8 | . | , | english | ... | 106 | no_NO | Norwegian - Norway | 9 | 7 | , | . | norwegian | | 107 | sv_FI | Swedish - Finland | 9 | 7 | , | | swedish | | 108 | zh_HK | Chinese - Hong Kong SAR | 3 | 3 | . | , | english | | 109 | el_GR | Greek - Greece | 11 | 9 | , | . | greek | +-----+-------+-------------------------------------+-----------------------+---------------------+---------------+--------------+------------------------+

SELECT * FROM information_schema.ENGINES\G; *************************** 1. row *************************** ENGINE: InnoDB SUPPORT: DEFAULT COMMENT: Supports transactions, row-level locking, and foreign keys TRANSACTIONS: YES XA: YES SAVEPOINTS: YES *************************** 2. row *************************** ENGINE: CSV SUPPORT: YES COMMENT: CSV storage engine TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 3. row *************************** ENGINE: MyISAM SUPPORT: YES COMMENT: MyISAM storage engine TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 4. row *************************** ENGINE: BLACKHOLE SUPPORT: YES COMMENT: /dev/null storage engine (anything you write to it disappears) TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 5. row *************************** ENGINE: FEDERATED SUPPORT: YES COMMENT: FederatedX pluggable storage engine TRANSACTIONS: YES XA: NO SAVEPOINTS: YES *************************** 6. row *************************** ENGINE: MRG_MyISAM SUPPORT: YES COMMENT: Collection of identical MyISAM tables TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 7. row *************************** ENGINE: ARCHIVE SUPPORT: YES COMMENT: Archive storage engine TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 8. row *************************** ENGINE: MEMORY SUPPORT: YES COMMENT: Hash based, stored in memory, useful for temporary tables TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 9. row *************************** ENGINE: PERFORMANCE_SCHEMA SUPPORT: YES COMMENT: Performance Schema TRANSACTIONS: NO XA: NO SAVEPOINTS: NO *************************** 10. row *************************** ENGINE: Aria SUPPORT: YES COMMENT: Crash-safe tables with MyISAM heritage TRANSACTIONS: NO XA: NO SAVEPOINTS: NO 10 rows in set (0.00 sec)

SELECT * FROM INFORMATION_SCHEMA.WSREP_BF_ABORT_HISTORY LIMIT 100; +----------------------------+---------------+------------------+-----------------+--------------+---------------------+--------------------+------------------+----------------------------+-----------+--------------+-------------+----------+-----------------+----------------+--------------+----------------------------+----------+---------+------------+------------------+ | TIME | VICTIM_TRX_ID | VICTIM_THREAD_ID | VICTIM_QUERY_ID | VICTIM_SEQNO | VICTIM_CLIENT_STATE | VICTIM_CLIENT_MODE | VICTIM_TRX_STATE | VICTIM_LOCK | BF_TRX_ID | BF_THREAD_ID | BF_QUERY_ID | BF_SEQNO | BF_CLIENT_STATE | BF_CLIENT_MODE | BF_TRX_STATE | BF_LOCK | SPACE_ID | PAGE_NO | INDEX_NAME | TABLE_NAME | +----------------------------+---------------+------------------+-----------------+--------------+---------------------+--------------------+------------------+----------------------------+-----------+--------------+-------------+----------+-----------------+----------------+--------------+----------------------------+----------+---------+------------+------------------+ | 2025-05-14 09:48:31.539207 | 378998 | 94 | 2365214 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379010 | 1 | 2365229 | 174271 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.597005 | 379044 | 81 | 2365344 | NULL | exec | local | certifying | REC|LOCK_X|NOT_GAP | 379060 | 1 | 2365419 | 174284 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.609301 | 379055 | 104 | 2365412 | NULL | exec | local | certifying | REC|LOCK_X|NOT_GAP | 379070 | 1 | 2365445 | 174289 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.725899 | 379134 | 101 | 2366437 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP | 379164 | 1 | 2366536 | 174307 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 147008 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789128 | 379094 | 131 | 2366355 | NULL | exec | local | certifying | REC|LOCK_X|NOT_GAP | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789140 | 379101 | 124 | 2366103 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789145 | 379093 | 82 | 2366113 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789148 | 379110 | 117 | 2366193 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789152 | 379126 | 111 | 2366201 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789156 | 379100 | 134 | 2366318 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789159 | 379109 | 93 | 2366334 | NULL | exec | local | executing | REC|LOCK_X|NOT_GAP|WAITING | 379195 | 1 | 2366599 | 174323 | exec | high priority | executing | REC|LOCK_X|NOT_GAP|WAITING | 12 | 4 | PRIMARY | `test`.`sbtest1` | | 2025-05-14 09:48:31.789163 | 379119 | 90 | 2366384 | NULL | exec | local | executing +----------------------------+---------------+------------------+-----------------+--------------+---------------------+--------------------+------------------+----------------------------+-----------+--------------+-------------+----------+-----------------+----------------+--------------+----------------------------+----------+---------+------------+------------------+ ...

CREATE TABLE majra(CHECK(x>0), x INT, y INT CHECK(y < 0), z INT, CONSTRAINT z CHECK(z>0), CONSTRAINT xyz CHECK(x<10 AND y<10 AND z<10)); Query OK, 0 rows affected (0.036 sec) SHOW CREATE TABLE majra; +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | majra | CREATE TABLE `majra` ( `x` int(11) DEFAULT NULL, `y` int(11) DEFAULT NULL CHECK (`y` < 0), `z` int(11) DEFAULT NULL, CONSTRAINT `CONSTRAINT_1` CHECK (`x` > 0), CONSTRAINT `z` CHECK (`z` > 0), CONSTRAINT `xyz` CHECK (`x` < 10 AND `y` < 10 AND `z` < 10) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 | +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.000 sec) SELECT * FROM information_schema.check_constraints WHERE table_name='majra'; +--------------------+-------------------+------------+-----------------+--------+------------------------------------+ | CONSTRAINT_CATALOG | CONSTRAINT_SCHEMA | TABLE_NAME | CONSTRAINT_NAME | LEVEL | CHECK_CLAUSE | +--------------------+-------------------+------------+-----------------+--------+------------------------------------+ | def | test | majra | y | Column | `y` < 0 | | def | test | majra | CONSTRAINT_1 | Table | `x` > 0 | | def | test | majra | z | Table | `z` > 0 | | def | test | majra | xyz | Table | `x` < 10 and `y` < 10 and `z` < 10 | +--------------------+-------------------+------------+-----------------+--------+------------------------------------+ 4 rows in set (0.001 sec)

SELECT * FROM INNODB_FT_INDEX_CACHE; +------------+--------------+-------------+-----------+--------+----------+ | WORD | FIRST_DOC_ID | LAST_DOC_ID | DOC_COUNT | DOC_ID | POSITION | +------------+--------------+-------------+-----------+--------+----------+ | and | 4 | 4 | 1 | 4 | 0 | | arrived | 4 | 4 | 1 | 4 | 20 | | ate | 1 | 1 | 1 | 1 | 4 | | everybody | 1 | 1 | 1 | 1 | 8 | | goldilocks | 4 | 4 | 1 | 4 | 9 | | hungry | 3 | 3 | 1 | 3 | 8 | | then | 4 | 4 | 1 | 4 | 4 | | wicked | 2 | 2 | 1 | 2 | 4 | | witch | 2 | 2 | 1 | 2 | 11 | +------------+--------------+-------------+-----------+--------+----------+ 9 rows in set (0.00 sec) INSERT INTO test.ft_innodb VALUES(3,'And she ate a pear'); SELECT * FROM INNODB_FT_INDEX_CACHE; +------------+--------------+-------------+-----------+--------+----------+ | WORD | FIRST_DOC_ID | LAST_DOC_ID | DOC_COUNT | DOC_ID | POSITION | +------------+--------------+-------------+-----------+--------+----------+ | and | 4 | 5 | 2 | 4 | 0 | | and | 4 | 5 | 2 | 5 | 0 | | arrived | 4 | 4 | 1 | 4 | 20 | | ate | 1 | 5 | 2 | 1 | 4 | | ate | 1 | 5 | 2 | 5 | 8 | | everybody | 1 | 1 | 1 | 1 | 8 | | goldilocks | 4 | 4 | 1 | 4 | 9 | | hungry | 3 | 3 | 1 | 3 | 8 | | pear | 5 | 5 | 1 | 5 | 14 | | she | 5 | 5 | 1 | 5 | 4 | | then | 4 | 4 | 1 | 4 | 4 | | wicked | 2 | 2 | 1 | 2 | 4 | | witch | 2 | 2 | 1 | 2 | 11 | +------------+--------------+-------------+-----------+--------+----------+

DESC information_schema.innodb_buffer_pool_stats; +----------------------------------+---------------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +----------------------------------+---------------------+------+-----+---------+-------+ | POOL_ID | bigint(21) unsigned | NO | | 0 | | | POOL_SIZE | bigint(21) unsigned | NO | | 0 | | | FREE_BUFFERS | bigint(21) unsigned | NO | | 0 | | | DATABASE_PAGES | bigint(21) unsigned | NO | | 0 | | | OLD_DATABASE_PAGES | bigint(21) unsigned | NO | | 0 | | | MODIFIED_DATABASE_PAGES | bigint(21) unsigned | NO | | 0 | | | PENDING_DECOMPRESS | bigint(21) unsigned | NO | | 0 | | | PENDING_READS | bigint(21) unsigned | NO | | 0 | | | PENDING_FLUSH_LRU | bigint(21) unsigned | NO | | 0 | | | PENDING_FLUSH_LIST | bigint(21) unsigned | NO | | 0 | | | PAGES_MADE_YOUNG | bigint(21) unsigned | NO | | 0 | | | PAGES_NOT_MADE_YOUNG | bigint(21) unsigned | NO | | 0 | | | PAGES_MADE_YOUNG_RATE | double | NO | | 0 | | | PAGES_MADE_NOT_YOUNG_RATE | double | NO | | 0 | | | NUMBER_PAGES_READ | bigint(21) unsigned | NO | | 0 | | | NUMBER_PAGES_CREATED | bigint(21) unsigned | NO | | 0 | | | NUMBER_PAGES_WRITTEN | bigint(21) unsigned | NO | | 0 | | | PAGES_READ_RATE | double | NO | | 0 | | | PAGES_CREATE_RATE | double | NO | | 0 | | | PAGES_WRITTEN_RATE | double | NO | | 0 | | | NUMBER_PAGES_GET | bigint(21) unsigned | NO | | 0 | | | HIT_RATE | bigint(21) unsigned | NO | | 0 | | | YOUNG_MAKE_PER_THOUSAND_GETS | bigint(21) unsigned | NO | | 0 | | | NOT_YOUNG_MAKE_PER_THOUSAND_GETS | bigint(21) unsigned | NO | | 0 | | | NUMBER_PAGES_READ_AHEAD | bigint(21) unsigned | NO | | 0 | | | NUMBER_READ_AHEAD_EVICTED | bigint(21) unsigned | NO | | 0 | | | READ_AHEAD_RATE | double | NO | | 0 | | | READ_AHEAD_EVICTED_RATE | double | NO | | 0 | | | LRU_IO_TOTAL | bigint(21) unsigned | NO | | 0 | | | LRU_IO_CURRENT | bigint(21) unsigned | NO | | 0 | | | UNCOMPRESS_TOTAL | bigint(21) unsigned | NO | | 0 | | | UNCOMPRESS_CURRENT | bigint(21) unsigned | NO | | 0 | | +----------------------------------+---------------------+------+-----+---------+-------+

SELECT PLUGIN_NAME, PLUGIN_DESCRIPTION, PLUGIN_MATURITY, PLUGIN_AUTH_VERSION FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_TYPE='STORAGE ENGINE' ORDER BY PLUGIN_MATURITY \G *************************** 1. row *************************** PLUGIN_NAME: FEDERATED PLUGIN_DESCRIPTION: FederatedX pluggable storage engine PLUGIN_MATURITY: Beta PLUGIN_AUTH_VERSION: 2.1 *************************** 2. row *************************** PLUGIN_NAME: Aria PLUGIN_DESCRIPTION: Crash-safe tables with MyISAM heritage PLUGIN_MATURITY: Gamma PLUGIN_AUTH_VERSION: 1.5 *************************** 3. row *************************** PLUGIN_NAME: PERFORMANCE_SCHEMA PLUGIN_DESCRIPTION: Performance Schema PLUGIN_MATURITY: Gamma PLUGIN_AUTH_VERSION: 0.1 *************************** 4. row *************************** PLUGIN_NAME: binlog PLUGIN_DESCRIPTION: This is a pseudo storage engine to represent the binlog in a transaction PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 5. row *************************** PLUGIN_NAME: MEMORY PLUGIN_DESCRIPTION: Hash based, stored in memory, useful for temporary tables PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 6. row *************************** PLUGIN_NAME: MyISAM PLUGIN_DESCRIPTION: MyISAM storage engine PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 7. row *************************** PLUGIN_NAME: MRG_MyISAM PLUGIN_DESCRIPTION: Collection of identical MyISAM tables PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 8. row *************************** PLUGIN_NAME: CSV PLUGIN_DESCRIPTION: CSV storage engine PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 9. row *************************** PLUGIN_NAME: InnoDB PLUGIN_DESCRIPTION: Supports transactions, row-level locking, and foreign keys PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.2.5 *************************** 10. row *************************** PLUGIN_NAME: BLACKHOLE PLUGIN_DESCRIPTION: /dev/null storage engine (anything you write to it disappears) PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 11. row *************************** PLUGIN_NAME: ARCHIVE PLUGIN_DESCRIPTION: Archive storage engine PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0 *************************** 12. row *************************** PLUGIN_NAME: partition PLUGIN_DESCRIPTION: Partition Storage Engine Helper PLUGIN_MATURITY: Stable PLUGIN_AUTH_VERSION: 1.0

SELECT name,subsystem,type,comment FROM INFORMATION_SCHEMA.INNODB_METRICS\G *************************** 1. row *************************** name: metadata_table_handles_opened subsystem: metadata type: counter comment: Number of table handles opened *************************** 2. row *************************** name: lock_deadlocks subsystem: lock type: value comment: Number of deadlocks *************************** 3. row *************************** name: lock_timeouts subsystem: lock type: value comment: Number of lock timeouts *************************** 4. row *************************** name: lock_rec_lock_waits subsystem: lock type: counter comment: Number of times enqueued into record lock wait queue *************************** 5. row *************************** name: lock_table_lock_waits subsystem: lock type: counter comment: Number of times enqueued into table lock wait queue *************************** 6. row *************************** name: lock_rec_lock_requests subsystem: lock type: counter comment: Number of record locks requested *************************** 7. row *************************** name: lock_rec_lock_created subsystem: lock type: counter comment: Number of record locks created *************************** 8. row *************************** name: lock_rec_lock_removed subsystem: lock type: counter comment: Number of record locks removed from the lock queue *************************** 9. row *************************** name: lock_rec_locks subsystem: lock type: counter comment: Current number of record locks on tables *************************** 10. row *************************** name: lock_table_lock_created subsystem: lock type: counter comment: Number of table locks created ... *************************** 207. row *************************** name: icp_attempts subsystem: icp type: counter comment: Number of attempts for index push-down condition checks *************************** 208. row *************************** name: icp_no_match subsystem: icp type: counter comment: Index push-down condition does not match *************************** 209. row *************************** name: icp_out_of_range subsystem: icp type: counter comment: Index push-down condition out of range *************************** 210. row *************************** name: icp_match subsystem: icp type: counter comment: Index push-down condition matches

SELECT * FROM INFORMATION_SCHEMA.KEYWORDS; +-------------------------------+ | WORD | +-------------------------------+ | && | | <= | | <> | | != | | >= | | << | | >> | | <=> | | ACCESSIBLE | | ACCOUNT | | ACTION | | ADD | | ADMIN | | AFTER | | AGAINST | | AGGREGATE | | ALL | | ALGORITHM | | ALTER | | ALWAYS | | ANALYZE | | AND | | ANY | | AS | | ASC | | ASCII | | ASENSITIVE | | AT | | ATOMIC | | AUTHORS | | AUTO_INCREMENT | | AUTOEXTEND_SIZE | | AUTO | | AVG | | AVG_ROW_LENGTH | | BACKUP | | BEFORE | | BEGIN | | BETWEEN | | BIGINT | | BINARY | | BINLOG | | BIT | | BLOB | | BLOCK | | BODY | | BOOL | | BOOLEAN | | BOTH | | BTREE | | BY | | BYTE | | CACHE | | CALL | | CASCADE | | CASCADED | | CASE | | CATALOG_NAME | | CHAIN | | CHANGE | | CHANGED | | CHAR | | CHARACTER | | CHARSET | | CHECK | | CHECKPOINT | | CHECKSUM | | CIPHER | | CLASS_ORIGIN | | CLIENT | | CLOB | | CLOSE | | COALESCE | | CODE | | COLLATE | | COLLATION | | COLUMN | | COLUMN_NAME | | COLUMNS | | COLUMN_ADD | | COLUMN_CHECK | | COLUMN_CREATE | | COLUMN_DELETE | | COLUMN_GET | | COMMENT | | COMMIT | | COMMITTED | | COMPACT | | COMPLETION | | COMPRESSED | | CONCURRENT | | CONDITION | | CONNECTION | | CONSISTENT | | CONSTRAINT | | CONSTRAINT_CATALOG | | CONSTRAINT_NAME | | CONSTRAINT_SCHEMA | | CONTAINS | | CONTEXT | | CONTINUE | | CONTRIBUTORS | | CONVERT | | CPU | | CREATE | | CROSS | | CUBE | | CURRENT | | CURRENT_DATE | | CURRENT_POS | | CURRENT_ROLE | | CURRENT_TIME | | CURRENT_TIMESTAMP | | CURRENT_USER | | CURSOR | | CURSOR_NAME | | CYCLE | | DATA | | DATABASE | | DATABASES | | DATAFILE | | DATE | | DATETIME | | DAY | | DAY_HOUR | | DAY_MICROSECOND | | DAY_MINUTE | | DAY_SECOND | | DEALLOCATE | | DEC | | DECIMAL | | DECLARE | | DEFAULT | | DEFINER | | DELAYED | | DELAY_KEY_WRITE | | DELETE | | DELETE_DOMAIN_ID | | DESC | | DESCRIBE | | DES_KEY_FILE | | DETERMINISTIC | | DIAGNOSTICS | | DIRECTORY | | DISABLE | | DISCARD | | DISK | | DISTINCT | | DISTINCTROW | | DIV | | DO | | DOUBLE | | DO_DOMAIN_IDS | | DROP | | DUAL | | DUMPFILE | | DUPLICATE | | DYNAMIC | | EACH | | ELSE | | ELSEIF | | ELSIF | | EMPTY | | ENABLE | | ENCLOSED | | END | | ENDS | | ENGINE | | ENGINES | | ENUM | | ERROR | | ERRORS | | ESCAPE | | ESCAPED | | EVENT | | EVENTS | | EVERY | | EXAMINED | | EXCEPT | | EXCHANGE | | EXCLUDE | | EXECUTE | | EXCEPTION | | EXISTS | | EXIT | | EXPANSION | | EXPIRE | | EXPORT | | EXPLAIN | | EXTENDED | | EXTENT_SIZE | | FALSE | | FAST | | FAULTS | | FEDERATED | | FETCH | | FIELDS | | FILE | | FIRST | | FIXED | | FLOAT | | FLOAT4 | | FLOAT8 | | FLUSH | | FOLLOWING | | FOLLOWS | | FOR | | FORCE | | FOREIGN | | FORMAT | | FOUND | | FROM | | FULL | | FULLTEXT | | FUNCTION | | GENERAL | | GENERATED | | GET_FORMAT | | GET | | GLOBAL | | GOTO | | GRANT | | GRANTS | | GROUP | | HANDLER | | HARD | | HASH | | HAVING | | HELP | | HIGH_PRIORITY | | HISTORY | | HOST | | HOSTS | | HOUR | | HOUR_MICROSECOND | | HOUR_MINUTE | | HOUR_SECOND | | ID | | IDENTIFIED | | IF | | IGNORE | | IGNORED | | IGNORE_DOMAIN_IDS | | IGNORE_SERVER_IDS | | IMMEDIATE | | IMPORT | | INTERSECT | | IN | | INCREMENT | | INDEX | | INDEXES | | INFILE | | INITIAL_SIZE | | INNER | | INOUT | | INSENSITIVE | | INSERT | | INSERT_METHOD | | INSTALL | | INT | | INT1 | | INT2 | | INT3 | | INT4 | | INT8 | | INTEGER | | INTERVAL | | INVISIBLE | | INTO | | IO | | IO_THREAD | | IPC | | IS | | ISOLATION | | ISOPEN | | ISSUER | | ITERATE | | INVOKER | | JOIN | | JSON | | JSON_TABLE | | KEY | | KEYS | | KEY_BLOCK_SIZE | | KILL | | LANGUAGE | | LAST | | LAST_VALUE | | LASTVAL | | LEADING | | LEAVE | | LEAVES | | LEFT | | LESS | | LEVEL | | LIKE | | LIMIT | | LINEAR | | LINES | | LIST | | LOAD | | LOCAL | | LOCALTIME | | LOCALTIMESTAMP | | LOCK | | LOCKED | | LOCKS | | LOGFILE | | LOGS | | LONG | | LONGBLOB | | LONGTEXT | | LOOP | | LOW_PRIORITY | | MASTER | | MASTER_CONNECT_RETRY | | MASTER_DELAY | | MASTER_GTID_POS | | MASTER_HOST | | MASTER_LOG_FILE | | MASTER_LOG_POS | | MASTER_PASSWORD | | MASTER_PORT | | MASTER_SERVER_ID | | MASTER_SSL | | MASTER_SSL_CA | | MASTER_SSL_CAPATH | | MASTER_SSL_CERT | | MASTER_SSL_CIPHER | | MASTER_SSL_CRL | | MASTER_SSL_CRLPATH | | MASTER_SSL_KEY | | MASTER_SSL_VERIFY_SERVER_CERT | | MASTER_USER | | MASTER_USE_GTID | | MASTER_HEARTBEAT_PERIOD | | MATCH | | MAX_CONNECTIONS_PER_HOUR | | MAX_QUERIES_PER_HOUR | | MAX_ROWS | | MAX_SIZE | | MAX_STATEMENT_TIME | | MAX_UPDATES_PER_HOUR | | MAX_USER_CONNECTIONS | | MAXVALUE | | MEDIUM | | MEDIUMBLOB | | MEDIUMINT | | MEDIUMTEXT | | MEMORY | | MERGE | | MESSAGE_TEXT | | MICROSECOND | | MIDDLEINT | | MIGRATE | | MINUS | | MINUTE | | MINUTE_MICROSECOND | | MINUTE_SECOND | | MINVALUE | | MIN_ROWS | | MOD | | MODE | | MODIFIES | | MODIFY | | MONITOR | | MONTH | | MUTEX | | MYSQL | | MYSQL_ERRNO | | NAME | | NAMES | | NATIONAL | | NATURAL | | NCHAR | | NESTED | | NEVER | | NEW | | NEXT | | NEXTVAL | | NO | | NOMAXVALUE | | NOMINVALUE | | NOCACHE | | NOCYCLE | | NO_WAIT | | NOWAIT | | NODEGROUP | | NONE | | NOT | | NOTFOUND | | NO_WRITE_TO_BINLOG | | NULL | | NUMBER | | NUMERIC | | NVARCHAR | | OF | | OFFSET | | OLD_PASSWORD | | ON | | ONE | | ONLINE | | ONLY | | OPEN | | OPTIMIZE | | OPTIONS | | OPTION | | OPTIONALLY | | OR | | ORDER | | ORDINALITY | | OTHERS | | OUT | | OUTER | | OUTFILE | | OVER | | OVERLAPS | | OWNER | | PACKAGE | | PACK_KEYS | | PAGE | | PAGE_CHECKSUM | | PARSER | | PARSE_VCOL_EXPR | | PATH | | PERIOD | | PARTIAL | | PARTITION | | PARTITIONING | | PARTITIONS | | PASSWORD | | PERSISTENT | | PHASE | | PLUGIN | | PLUGINS | | PORT | | PORTION | | PRECEDES | | PRECEDING | | PRECISION | | PREPARE | | PRESERVE | | PREV | | PREVIOUS | | PRIMARY | | PRIVILEGES | | PROCEDURE | | PROCESS | | PROCESSLIST | | PROFILE | | PROFILES | | PROXY | | PURGE | | QUARTER | | QUERY | | QUICK | | RAISE | | RANGE | | RAW | | READ | | READ_ONLY | | READ_WRITE | | READS | | REAL | | REBUILD | | RECOVER | | RECURSIVE | | REDO_BUFFER_SIZE | | REDOFILE | | REDUNDANT | | REFERENCES | | REGEXP | | RELAY | | RELAYLOG | | RELAY_LOG_FILE | | RELAY_LOG_POS | | RELAY_THREAD | | RELEASE | | RELOAD | | REMOVE | | RENAME | | REORGANIZE | | REPAIR | | REPEATABLE | | REPLACE | | REPLAY | | REPLICA | | REPLICAS | | REPLICA_POS | | REPLICATION | | REPEAT | | REQUIRE | | RESET | | RESIGNAL | | RESTART | | RESTORE | | RESTRICT | | RESUME | | RETURNED_SQLSTATE | | RETURN | | RETURNING | | RETURNS | | REUSE | | REVERSE | | REVOKE | | RIGHT | | RLIKE | | ROLE | | ROLLBACK | | ROLLUP | | ROUTINE | | ROW | | ROWCOUNT | | ROWNUM | | ROWS | | ROWTYPE | | ROW_COUNT | | ROW_FORMAT | | RTREE | | SAVEPOINT | | SCHEDULE | | SCHEMA | | SCHEMA_NAME | | SCHEMAS | | SECOND | | SECOND_MICROSECOND | | SECURITY | | SELECT | | SENSITIVE | | SEPARATOR | | SEQUENCE | | SERIAL | | SERIALIZABLE | | SESSION | | SERVER | | SET | | SETVAL | | SHARE | | SHOW | | SHUTDOWN | | SIGNAL | | SIGNED | | SIMPLE | | SKIP | | SLAVE | | SLAVES | | SLAVE_POS | | SLOW | | SNAPSHOT | | SMALLINT | | SOCKET | | SOFT | | SOME | | SONAME | | SOUNDS | | SOURCE | | STAGE | | STORED | | SPATIAL | | SPECIFIC | | REF_SYSTEM_ID | | SQL | | SQLEXCEPTION | | SQLSTATE | | SQLWARNING | | SQL_BIG_RESULT | | SQL_BUFFER_RESULT | | SQL_CACHE | | SQL_CALC_FOUND_ROWS | | SQL_NO_CACHE | | SQL_SMALL_RESULT | | SQL_THREAD | | SQL_TSI_SECOND | | SQL_TSI_MINUTE | | SQL_TSI_HOUR | | SQL_TSI_DAY | | SQL_TSI_WEEK | | SQL_TSI_MONTH | | SQL_TSI_QUARTER | | SQL_TSI_YEAR | | SSL | | START | | STARTING | | STARTS | | STATEMENT | | STATS_AUTO_RECALC | | STATS_PERSISTENT | | STATS_SAMPLE_PAGES | | STATUS | | STOP | | STORAGE | | STRAIGHT_JOIN | | STRING | | SUBCLASS_ORIGIN | | SUBJECT | | SUBPARTITION | | SUBPARTITIONS | | SUPER | | SUSPEND | | SWAPS | | SWITCHES | | SYSDATE | | SYSTEM | | SYSTEM_TIME | | TABLE | | TABLE_NAME | | TABLES | | TABLESPACE | | TABLE_CHECKSUM | | TEMPORARY | | TEMPTABLE | | TERMINATED | | TEXT | | THAN | | THEN | | TIES | | TIME | | TIMESTAMP | | TIMESTAMPADD | | TIMESTAMPDIFF | | TINYBLOB | | TINYINT | | TINYTEXT | | TO | | TRAILING | | TRANSACTION | | TRANSACTIONAL | | THREADS | | TRIGGER | | TRIGGERS | | TRUE | | TRUNCATE | | TYPE | | TYPES | | UNBOUNDED | | UNCOMMITTED | | UNDEFINED | | UNDO_BUFFER_SIZE | | UNDOFILE | | UNDO | | UNICODE | | UNION | | UNIQUE | | UNKNOWN | | UNLOCK | | UNINSTALL | | UNSIGNED | | UNTIL | | UPDATE | | UPGRADE | | USAGE | | USE | | USER | | USER_RESOURCES | | USE_FRM | | USING | | UTC_DATE | | UTC_TIME | | UTC_TIMESTAMP | | VALUE | | VALUES | | VARBINARY | | VARCHAR | | VARCHARACTER | | VARCHAR2 | | VARIABLES | | VARYING | | VIA | | VIEW | | VIRTUAL | | VISIBLE | | VERSIONING | | WAIT | | WARNINGS | | WEEK | | WEIGHT_STRING | | WHEN | | WHERE | | WHILE | | WINDOW | | WITH | | WITHIN | | WITHOUT | | WORK | | WRAPPER | | WRITE | | X509 | | XOR | | XA | | XML | | YEAR | | YEAR_MONTH | | ZEROFILL | | || | +-------------------------------+ 694 rows in set (0.000 sec)

Information Schema

TIME_MS column in INFORMATION_SCHEMA.PROCESSLIST

Information Schema Tables

Information Schema ALL_PLUGINS Table

Description

Example

Information Schema APPLICABLE_ROLES Table

Information Schema CATALOG Table

Example

See Also

Information Schema CHARACTER_SETS Table

Example

Information Schema COLLATION_CHARACTER_SET_APPLICABILITY Table

Example

Information Schema COLUMN_PRIVILEGES Table

Example

Information Schema DISKS Table

Description

Example

See Also

Information Schema ENABLED_ROLES Table

Examples

Information Schema GLOBAL_STATUS and SESSION_STATUS Tables

Information Schema GLOBAL_VARIABLES and SESSION_VARIABLES Tables

Example

Information Schema INDEX_STATISTICS Table

Information Schema KEY_CACHES Table

Example

Information Schema KEY_PERIOD_USAGE Table

Information Schema LOCALES Table

Description

Example

Information Schema MROONGA_STATS Table

Information Schema OPTIMIZER_TRACE Table

Description

Information Schema PERIODS Table

Information Schema PROFILING Table

Information Schema QUERY_RESPONSE_TIME Table

Description

Example

Information Schema REFERENTIAL_CONSTRAINTS Table

Information Schema SCHEMA_PRIVILEGES Table

Information Schema SLAVE_STATUS Table

Information Schema SPIDER_ALLOC_MEM Table

Information Schema TABLE_CONSTRAINTS Table

Information Schema TABLE_PRIVILEGES Table

See Also

Information Schema TABLE_STATISTICS Table

Example

Information Schema TABLESPACES Table

Information Schema THREAD_POOL_GROUPS Table

Information Schema USER_PRIVILEGES Table

Information Schema USERS Table

Information Schema WSREP_CERT_KEYS

Exclusive

Reference

Update

Shared

Information Schema WSREP_CERT_KEYS_HISTORY

Information Schema WSREP_CONNECTIONS

Information Schema WSREP_THD_STATE_HISTORY

Information Schema InnoDB Tables

Information Schema INNODB_BUFFER_POOL_PAGES_INDEX Table

Information Schema INNODB_CMPMEM and INNODB_CMPMEM_RESET Tables

Example

See Also

Information Schema

Information Schema Tables

TIME_MS column in INFORMATION_SCHEMA.PROCESSLIST

Information Schema ALL_PLUGINS Table

Description

Example

Information Schema MROONGA_STATS Table

Information Schema WSREP_THD_STATE_HISTORY

Information Schema InnoDB Tables

Information Schema WSREP_CONNECTIONS

Information Schema CATALOG Table

Example

See Also

Information Schema QUERY_RESPONSE_TIME Table