mysql Schema

The mysql schema contains TiDB system tables. The design is similar to the mysql schema in MySQL, where tables such as mysql.user can be edited directly. It also contains a number of tables which are extensions to MySQL.

Grant system tables

These system tables contain grant information about user accounts and their privileges:

  • user: user accounts, global privileges, and other non-privilege columns
  • db: database-level privileges
  • tables_priv: table-level privileges
  • columns_priv: column-level privileges
  • password_history: password change history
  • default_roles: the default roles for a user
  • global_grants: dynamic privileges
  • global_priv: the authentication information based on certificates
  • role_edges: the relationship between roles

Cluster status system tables

  • The tidb table contains some global information about TiDB:

    • bootstrapped: whether the TiDB cluster has been initialized. Note that this value is read-only and cannot be modified.
    • tidb_server_version: the version information of TiDB when it is initialized. Note that this value is read-only and cannot be modified.
    • system_tz: the system time zone of TiDB.
    • new_collation_enabled: whether TiDB has enabled the new framework for collations. Note that this value is read-only and cannot be modified.

Server-side help system tables

Currently, the help_topic is NULL.

Statistics system tables

  • stats_buckets: the buckets of statistics
  • stats_histograms: the histograms of statistics
  • stats_top_n: the TopN of statistics
  • stats_meta: the meta information of tables, such as the total number of rows and updated rows
  • stats_extended: extended statistics, such as the order correlation between columns
  • stats_feedback: the query feedback of statistics
  • stats_fm_sketch: the FMSketch distribution of the histogram of the statistics column
  • analyze_options: the default analyze options for each table
  • column_stats_usage: the usage of column statistics
  • schema_index_usage: the usage of indexes
  • analyze_jobs: the ongoing statistics collection tasks and the history task records within the last 7 days
  • bind_info: the binding information of execution plans
  • capture_plan_baselines_blacklist: the blocklist for the automatic binding of the execution plan

GC worker system tables

mysql - 图1

Note

The GC worker system tables are only applicable to TiDB Self-Hosted and not available on TiDB Cloud.

  • gc_delete_range: the KV range to be deleted
  • gc_delete_range_done: the deleted KV range
  • table_cache_meta: stores the metadata of cached tables

mysql - 图2

Note

The TTL related system tables are not available on TiDB Serverless clusters.

  • mysql.tidb_ttl_table_status the previously executed TTL job and ongoing TTL job for all TTL tables
  • mysql.tidb_ttl_task the current ongoing TTL subtasks
  • mysql.tidb_ttl_job_history the execution history of TTL tasks in the last 90 days
  • tidb_mdl_view：a view of metadata locks. You can use it to view information about the currently blocked DDL statements
  • tidb_mdl_info：used internally by TiDB to synchronize metadata locks across nodes
  • tidb_ddl_history: the history records of DDL statements
  • tidb_ddl_jobs: the metadata of DDL statements that are currently being executed by TiDB
  • tidb_ddl_reorg: the metadata of physical DDL statements (such as adding indexes) that are currently being executed by TiDB

Miscellaneous system tables

mysql - 图3

Note

The tidb, expr_pushdown_blacklist, opt_rule_blacklist, and table_cache_meta system tables are only applicable to TiDB Self-Hosted and not available on TiDB Cloud.

  • GLOBAL_VARIABLES: global system variable table
  • expr_pushdown_blacklist: the blocklist for expression pushdown
  • opt_rule_blacklist: the blocklist for logical optimization rules
  • tidb_timers: the metadata of internal timers