tidb v2.1.14 Release Notes

Release Date: 2019-07-04 // over 4 years ago
    • ๐Ÿ›  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 step 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