The TiDB configuration file supports more options than command line options. You can find the default configuration file in config/config.toml.example and rename it to
This document describes the options that are not involved in command line options. For command line options, see here.
KILLstatement to be MySQL compatible
KILL xxxin TiDB differs from the behavior in MySQL. TiDB requires the
TIDBkeyword, as in
KILL TIDB xxx. If
compatible-kill-queryis set to true, the
TIDBkeyword is not needed.
compatible-kill-queryif you are certain that the connection you refer to in your
KILLstatement is on the same server to which you send the
Configuration about log.
expensiveoperation and outputs log with the
query-log-max-len, the statement is truncated to output
Configuration about security.
--ssl-keyat the same time, TiDB authenticates the client certificate based on the list of trusted CAs specified by this option when the client presents the certificate. If the authentication fails, the connection is terminated.
--ssl-keyat the same time, TiDB allows (but not forces) the client to securely connect to TiDB using TLS
Configuration about performance.
n, and then TiDB uses
stmt-count-limit, TiDB returns the
statement count 5001 exceeds the transaction limitation, autocommit = falseerror.
keepalivein the TCP layer
joinstatement without any condition (the
wherefield) of both sides tables by default; if you set the value to false, the server refuses to execute when such a
stats-leasetime, TiDB checks the statistics for updates and updates them to the memory if updates exist
20 * stats-leasetime, TiDB updates the total number of rows generated by DML and the number of modified rows to the system table
stats-lease, TiDB checks for tables and indexes that need to be automatically analyzed
stats-lease, TiDB checks for column statistics that need to be loaded to the memory
200 * stats-lease, TiDB writes the feedback cached in the memory to the system table
5 * stats-lease, TiDB reads the feedback in the system table, and updates the statistics cached in the memory
stats-lease is set to 0, TiDB periodically reads the feedback in the system table, and updates the statistics cached in the memory every three seconds. But TiDB no longer automatically modifies the following statistics-related system tables:
mysql.stats_meta: TiDB no longer automatically records the number of table rows that are modified by the transaction or updates it to this system table
mysql.stats_top_n: TiDB no longer automatically analyzes or proactively updates statistics
mysql.stats_feedback: TiDB no longer updates the statistics of the tables and indexes according to a part of statistics returned by the queried data
feedback-probability, to update statistics
The Plan Cache configuration of the
Configuration about the transaction latch. It is recommended to enable it when many local transaction conflicts occur.