You are viewing the documentation of an older version of the TiDB database (TiDB v5.4).

It is recommended that you use the latest LTS version of the TiDB database.

TiDB 2.1.14 Release Notes

Release date: July 04, 2019

TiDB version: 2.1.14

TiDB Ansible version: 2.1.14


  • Fix wrong query results caused by column pruning in some cases #11019
  • Fix the wrongly displayed information in db and info columns of show processlist #11000
  • Fix the issue that MAX_EXECUTION_TIME as a SQL hint and global variable does not work in some cases #10999
  • Support automatically adjust the incremental gap allocated by auto-increment ID based on the load #10997
  • Fix the issue that the Distsql memory information of MemTracker is not correctly cleaned when a query ends #10971
  • Add the MEM column in the information_schema.processlist table to describe the memory usage of a query #10896
  • Add the max_execution_time global system variable to control the maximum execution time of a query #10940
  • Fix the panic caused by using unsupported aggregate functions #10911
  • Add an automatic rollback feature for the last transaction when the load data statement fails #10862
  • Fix the issue that TiDB returns a wrong result in some cases when the OOMAction configuration item is set to Cancel #11016
  • Disable the TRACE statement to avoid the TiDB panic issue #11039
  • Add the mysql.expr_pushdown_blacklist system table that dynamically enables/disables pushing down specific functions to Coprocessor #10998
  • Fix the issue that the ANY_VALUE function does not work in the ONLY_FULL_GROUP_BY mode #10994
  • Fix the incorrect evaluation caused by not doing a deep copy when evaluating the user variable of the string type #11043


  • Optimize processing the empty callback when processing the Raftstore message to avoid sending unnecessary message #4682


  • Adjust the log output level from Error to Warning when reading an invalid configuration item #1577


TiDB Binlog

  • Reparo
    • Add the safe-mode configuration item, and support importing duplicated data after this item is enabled #662
  • Pump
    • Add the stop-write-at-available-space configuration item to limit the available binlog space #659
    • Fix the issue that Garbage Collector does not work sometimes when the number of LevelDB L0 files is 0 #648
    • Optimize the algorithm of deleting log files to speed up releasing the space #648
  • Drainer
    • Fix the failure to update BIT columns in the downstream #655

TiDB Ansible

  • Add the precheck feature for the ansible command and its jmespath and jinja2 dependency packages #807
  • Add the stop-write-at-available-space parameter (10 GiB by default) in Pump, and stop writing binlog files in Pump when the available disk space is less than the parameter value #807
Was this page helpful?