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.

The information_schema is a standard-compliant database available in every MariaDB instance, providing metadata about all other databases, tables, columns, and server-level objects.

Information Schema Tables

Provides a comprehensive list of all tables available within the information_schema, including their purpose and the metadata they provide.

TIME_MS column in INFORMATION_SCHEMA.PROCESSLIST

Details the TIME_MS column in the INFORMATION_SCHEMA.PROCESSLIST table, which provides high-resolution timing for active server processes.

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 @TIMESTAMP. This means that it can be reliably used also for threads that change @TIMESTAMP (such as the replication SQL thread). See also MySQL Bug #22047.

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 SHOW SLAVE STATUS.

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

_{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 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 Information Schema APPLICABLE_ROLES table shows the role authorizations that the current user may use.

It contains the following columns:

Column

Description

GRANTEE

The current role is in the Information Schema table.

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

Information Schema CATALOG Table

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

The CATALOG table stores information about on the server.

It contains the following columns:

Column

Description

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

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.

_{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 COLLATION_CHARACTER_SET_APPLICABILITY table shows which are associated with which collations.

It contains the following columns:

Column

Description

Information Schema COLUMN_PRIVILEGES Table

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

The COLUMN_PRIVILEGES table contains column privilege information derived from the grant table.

It has the following columns:

Column

Description

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 DISKS table is created when the plugin is enabled, and shows metadata about disks on the system.

This plugin requires the .

The table contains the following columns:

Column

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

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.

Information Schema FEEDBACK Table

The Information Schema FEEDBACK table is created when the Feedback Plugin is enabled and contains the usage data collected for submission.

The FEEDBACK table is created when the is enabled, and contains the complete contents submitted by the plugin.

It contains two columns:

Column

Description

Information Schema FILE_KEY_MANAGEMENT_KEYS Table

The Information Schema FILES table provides information about files stored in tablespaces, such as those used by the InnoDB storage engine.

This table is available from MariaDB Enterprise Server 11.8.

The INFORMATION_SCHEMA.FILE_KEY_MANAGEMENT_KEYS table lists key ID and latest key version for keys managed by the file_key_management plugin. The table's contents can be queried directly, or viewed using the SHOW FILE_KEY_MANAGEMENT_KEYS statement.

You can also can reload the data from the key file into the cache by issuing this statement:

FLUSH FILE_KEY_MANAGEMENT_KEYS

This functionality is provided by the file_key_management plugin.

This Information Schema table allows to query the key numbers and key versions which are currently in the cache (which can be different to the file). It also allows to verify which keys are in use when joining the table with INNODB_TABLESPACES_ENCRYPTION.

Information Schema HASHICORP_KEY_MANAGEMENT_CACHE Table

The Information Schema HASHICORP_KEY_MANAGEMENT_CACHE table provides information about keys managed by the HashiCorp Key Management plugin.

This table is available from MariaDB 12.3.

The INFORMATION_SCHEMA.HASHICORP_KEY_MANAGEMENT_CACHE table lists the Key ID and the latest Key Version for keys managed by the HashiCorp Key Management plugin. The table's contents can be queried directly, or viewed using the SHOW HASHICORP_KEY_MANAGEMENT_CACHE statement.

You can reload the data from the Vault server into the cache by issuing this statement:

FLUSH HASHICORP_KEY_MANAGEMENT_CACHE

This functionality is provided by the HashiCorp Key Management plugin.

This Information Schema table allows you to query the key numbers and key versions which are currently in the cache.

Columns

The table contains the following columns:

Column Name

Description

Accessing the INFORMATION_SCHEMA.HASHICORP_KEY_MANAGEMENT_CACHE table requires the PROCESS privilege.

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 Information Schema GLOBAL_STATUS and SESSION_STATUS tables store a record of all status variables and their global and session values respectively. This is the same information as displayed by the SHOW STATUS commands SHOW GLOBAL STATUS and SHOW SESSION STATUS.

They contain the following columns:

Column

Description

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

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

_{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 KEY_CACHES table shows statistics about the .

It contains the following columns:

Column Name

Description

Information Schema KEY_COLUMN_USAGE Table

The Information Schema KEY_COLUMN_USAGE table details which columns in a table are constrained by keys, such as primary or foreign keys.

The KEY_COLUMN_USAGE table shows which key columns have constraints.

It contains the following columns:

Column

Description

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 Information Schema KEY_PERIOD_USAGE table shows information about Application-Time Periods.

It contains the following columns:

Column

Description

CONSTRAINT_CATALOG

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

Information Schema LOCALES Table

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

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

It contains the following columns:

Column

Description

Information Schema MROONGA_STATS Table

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

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

Column

Description

VERSION

Mroonga version.

This table always contains 1 row.

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

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 Information Schema OPTIMIZER_TRACE table contains information.

It contains the following columns:

Column

Description

QUERY

Structure:

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

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 Information Schema PERIODS table provides information about Application-Time Periods.

It contains the following columns:

Column

Description

TABLE_CATALOG

_{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.

_{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 Information Schema REFERENTIAL_CONSTRAINTS table contains information about foreign keys. The single columns are listed in the KEY_COLUMN_USAGE table.

It has the following columns:

Column

Description

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

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

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 Information Schema SLAVE_STATUS table contains replica status information, similar to SHOW REPLICA STATUS.

See SHOW REPLICA STATUS for column descriptions.

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

Information Schema SPATIAL_REF_SYS Table

The Information Schema SPATIAL_REF_SYS table stores information about available Spatial Reference Systems (SRS) for geometry data.

Description

The Information Schema SPATIAL_REF_SYS table stores information on each spatial reference system used in the database.

It contains the following columns:

Column

Type

Null

Description

Note: See .

table.

_{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 Information Schema SPIDER_ALLOC_MEM table is installed along with the Spider storage engine. It shows information about Spider's memory usage.

It contains the following columns:

Column

Description

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

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

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

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 .

_{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 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

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.

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

Column

Description

Information Schema THREAD_POOL_QUEUES Table

The Information Schema THREAD_POOL_QUEUES table shows the status of the queues within the thread pool, detailing pending connections.

This table is available from MariaDB 10.5.

The table provides information about thread pool queues, and contains the following columns:

Column

Description

GROUP_ID

the thread group this row is showing data for

POSITION

Setting will provides better queueing time statistics by using a high precision timestamp, at a small performance cost, for the time when the connection was added to the queue. This timestamp helps calculate the queuing time shown in the table.

Setting will give each group its own dedicated listener, and the listener thread will not pick up work items. As a result, the queueing time in the table will be more exact, since IO requests are immediately dequeued from poll, without delay.

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

Information Schema THREAD_POOL_STATS Table

The Information Schema THREAD_POOL_STATS table provides performance statistics for the thread pool, such as thread creation and efficiency.

This table is available from MariaDB 10.5.

The table provides performance counter information for the thread pool, and contains the following columns:

Column

Description

GROUP_ID

the thread group this row is showing data for

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

Information Schema THREAD_POOL_WAITS Table

The Information Schema THREAD_POOL_WAITS table lists the number of times threads in the thread pool have waited for various events.

This table is available from MariaDB 10.5.

The table provides wait counters for the thread pool, and contains the following columns:

Column

Description

REASON

name of the reason for waiting, e.g. ROW_LOCK, DISKIO, NET ...

COUNT

how often a wait for this specific reason has happened so far

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

Information Schema TRIGGERED_UPDATE_COLUMNS

The Information Schema TRIGGERED_UPDATE_COLUMNS table identifies which columns are modified by the SET clause of a specific trigger.

The TRIGGERED_UPDATE_COLUMNS table shows columns specified in for operations.

Columns are displayed only if the user has non-SELECT on the columns.

It 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

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.

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_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 WSREP_CERT_KEYS 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 .

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_MEMBERSHIP Table

The Information Schema WSREP_MEMBERSHIP table lists the current members of the Galera Cluster, including their node UUIDs, names, and IP addresses.

The WSREP_STATUS table makes node cluster membership information available through the . The same information can be returned using the statement. Only users with the can access information from this table.

The WSREP_MEMBERSHIP table is part of the .

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

Information Schema WSREP_STATUS Table

The Information Schema WSREP_STATUS table provides a comprehensive view of the Galera Cluster status variables, similar to SHOW STATUS LIKE 'wsrep%'

The WSREP_STATUS table makes node cluster status information available through the . The same information can be returned using the statement. Only users with the privilege can access information from this table.

The WSREP_STATUS table is part of the .

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

Information Schema WSREP_THD_STATE

The Information Schema WSREP_THD_STATE table displays the internal state of Galera threads, helping to monitor replication progress and locking.

This table contains execution state information for Galera threads, and has these columns:

ID - Thread ID
OS_THREAD_ID - Os thread ID

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 .

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 Table

The Information Schema INNODB_BUFFER_POOL_PAGES table provides a record for each page in the buffer pool, specific to the XtraDB engine.

The INNODB_BUFFER_POOL_PAGES table is a Percona enhancement, and is only available for XtraDB, not InnoDB (see ). It contains a record for each page in the .

It has the following columns:

Column

Description

Information Schema INNODB_BUFFER_POOL_PAGES_BLOB Table

The INNODB_BUFFER_POOL_PAGES_BLOB table contains information about blob pages in the buffer pool, only available for XtraDB.

The INNODB_BUFFER_POOL_PAGES_BLOB table is a Percona enhancement, and is only available for XtraDB, not InnoDB (see ). It contains information about blob pages.

It has the following columns:

Column

Description

Information Schema INNODB_FT_CONFIG Table

The Information Schema INNODB_FT_CONFIG table displays metadata about the configuration of an InnoDB FULLTEXT index, such as the internal cache size.

The INNODB_FT_CONFIG table contains InnoDB metadata.

The SUPER is required to view the table, and it also requires the system variable to be set.

It has the following columns:

Column

Description

Information Schema INNODB_FT_DELETED Table

The INNODB_FT_DELETED table lists document IDs of rows that have been deleted from an InnoDB FULLTEXT index but not yet removed from the index files.

The INNODB_FT_DELETED table contains rows that have been deleted from an InnoDB . This information is then used to filter results on subsequent searches, removing the need to expensively reorganise the index each time a row is deleted.

The fulltext index is then only reorganized when an statement is underway. The related table contains rows being deleted while an OPTIMIZE TABLE is in the process of running.

The SUPER is required to view the table, and it also requires the system variable to be set.

It has the following column:

Information Schema INNODB_LOCK_WAITS Table

The Information Schema INNODB_LOCK_WAITS table maps blocked transactions to the transactions that are blocking them, aiding in deadlock analysis.

The INNODB_LOCK_WAITS table contains information about blocked InnoDB transactions. The PROCESS is required to view the table.

It contains the following columns:

Column

Description

Information Schema INNODB_MUTEXES Table

The Information Schema INNODB_MUTEXES table displays statistics about InnoDB mutex and read-write lock waits, helping to identify internal contention.

The INNODB_MUTEXES table monitors mutex and rw locks waits. It has the following columns:

Column

Description

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.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 +----------------------------+---------------+------------------+-----------------+--------------+---------------------+--------------------+------------------+----------------------------+-----------+--------------+-------------+----------+-----------------+----------------+--------------+----------------------------+----------+---------+------------+------------------+ ...

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.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

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

Information Schema INNODB_METRICS Table

The Information Schema INNODB_METRICS table contains a wide range of low-level performance metrics and counters for the InnoDB storage engine.

The Information Schema INNODB_METRICS table contains a list of useful InnoDB performance metrics. Each row in the table represents an instrumented counter that can be stopped, started and reset, and which can be grouped together by module.

The PROCESS privilege is required to view the table.

It has the following columns:

Column

Description

Note: In MariaDB 10.4 and earlier the ENABLED column was called STATUS.

Most of the counters are disabled by default. To enable them, use the system variable. You can either enable a variable by its name, for example:

or enable a number of counters grouped by module. The SUBSYSTEM field indicates which counters are grouped together, but the following module names need to be used:

Module Name

Subsystem Field

There are four counters in the icp subsystem:

To enable them all, use the associated module name from the table above, module_icp.

The % wildcard, used to represent any number of characters, can also be used when naming counters, for example:

To disable counters, use the system variable, using the same naming rules as described above for enabling.

Counter status is not persistent, and will be reset when the server restarts. It is possible to use the options on the command line, or the innodb_monitor_enable option only in a configuration file.

Counters can also be reset. Resetting sets all the *_COUNT_RESET values to zero, while leaving the *_COUNT values, which perform counts since the counter was enabled, untouched. Resetting is performed with the (for individual counters) and (for all counters) system variables.

From MariaDB 10.6, the interface was simplified by removing the following variables:

buffer_LRU_batches_flush
buffer_LRU_batch_flush_pages
buffer_LRU_batches_evict
buffer_LRU_batch_evict_pages

And by making the following reflect the status variables:

buffer_LRU_batch_flush_total_pages:
buffer_LRU_batch_evict_total_pages:

The intention is to eventually remove the interface entirely (see ).

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

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)