Before MariaDB 10.0, the MySQL/MariaDB optimizer relied on storage engines (e.g. InnoDB) to provide statistics for the query optimizer. This approach worked; however it had some deficiencies:
Engine-independent table statistics lift these limitations.
Use or update of data from these tables is controlled by use_stat_tables variable. Possible values are listed below:
|'never'||The optimizer doesn't use data from statistics tables. Default for MariaDB 10.4.0 and below.|
|'complementary'||The optimizer uses data from statistics tables if the same kind of data is not provided by the storage engine.|
|'preferably'||Prefer the data from statistics tables, if it's not available there, use the data from the storage engine.|
ANALYZE TABLE statement can be used to collect table statistics. For example:
ANALYZE TABLE table_name;
ANALYZE TABLE statement is executed, MariaDB makes a call to the table's storage engine, and the storage engine collects its own statistics for the table. The specific behavior depends on the storage engine. For InnoDB, see InnoDB Persistent Statistics for more information.
ANALYZE TABLE statement is executed, MariaDB may also collect engine-independent statistics for the table. The specific behavior depends on the value of the
use_stat_tables system variable. Engine-independent statistics will only be collected by the
ANALYZE TABLE statement if one of the following is true:
use_stat_tablessystem variable is set to
ANALYZE TABLEstatement includes the
In MariaDB 10.4 and later, the
use_stat_tables system variable is set to
preferably_for_queries by default. With this value, engine-independent statistics are used by default, but they are not collected by default. If you want to use engine-independent statistics with the default configuration, then you will have to collect them by executing the
ANALYZE TABLE statement and by specifying the
PERSISTENT FOR clause. It is recommended to collect engine-independent statistics on as-needed basis, so typically one will not have engine-independent statistics for all indexes/all columns.
Engine-independent statistics are collected by doing full table and full index scans, and this process can be quite expensive.
The syntax for the
ANALYZE TABLE statement has been extended with the
PERSISTENT FOR clause. This clause allows one to collect engine-independent statistics only for particular columns or indexes. This clause also allows one to collect engine-independent statistics, regardless of the value of the
use_stat_tables system variable. For example:
ANALYZE TABLE table_name PERSISTENT FOR ALL;
-- update all engine-independent statistics for all columns and indexes ANALYZE TABLE tbl PERSISTENT FOR ALL; -- update specific columns and indexes: ANALYZE TABLE tbl PERSISTENT FOR COLUMNS (col1,col2,...) INDEXES (idx1,idx2,...); -- empty lists are allowed: ANALYZE TABLE tbl PERSISTENT FOR COLUMNS (col1,col2,...) INDEXES (); ANALYZE TABLE tbl PERSISTENT FOR COLUMNS () INDEXES (idx1,idx2,...); -- the following will only update mysql.table_stats fields: ANALYZE TABLE tbl PERSISTENT FOR COLUMNS () INDEXES (); -- when use_stat_tables is set to 'COMPLEMENTARY' or 'PREFERABLY', -- a simple ANALYZE TABLE collects engine-independent statistics for all columns and indexes. SET SESSION use_stat_tables='COMPLEMENTARY'; ANALYZE TABLE tbl;
It is possible to update statistics tables manually. One should modify the table(s) with regular INSERT/UPDATE/DELETE statements. Statistics data will be re-read when the tables are re-opened. One way to force all tables to be re-opened is to issue FLUSH TABLES command.
A few scenarios where one might need to update statistics tables manually:
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.