TiDB 2.1.19 Release Notes
Release date: December 27, 2019
TiDB version: 2.1.19
TiDB Ansible version: 2.1.19
TiDB
- SQL Optimizer
- Optimize the scenario of
select max(_tidb_rowid) from tto avoid full table scan #13294 - Fix the incorrect results caused by the incorrect value assigned to the user variable in the query and the push-down of predicates #13230
- Fix the issue that the statistics are not accurate because a data race occurs when statistics are updated #13690
- Fix the issue that the result is incorrect when the
UPDATEstatement contains both a sub-query and a stored generated column; fix theUPDATEstatement execution error when this statement contains two same-named tables from different databases #13357 - Fix the issue that the query plan might be incorrectly selected because the
PhysicalUnionScanoperator incorrectly sets the statistics #14134 - Remove the
minAutoAnalyzeRatioconstraint to make the automaticANALYZEmore timely #14013 - Fix the issue that the estimated number of rows is greater than
1when theWHEREclause contains an equal condition on the unique key #13385
- Optimize the scenario of
- SQL Execution Engine
- Fix the precision overflow when using
int64as the intermediate result ofunit64inConvertJSONToInt#13036 - Fix the issue that when the
SLEEPfunction is in a query (for example,select 1 from (select sleep(1)) t;)), column pruning causessleep(1)in the query to be invalid #13039 - Reduce memory overhead by reusing
Chunkin theINSERT ON DUPLICATE UPDATEstatement #12999 - Add more transaction-related fields for the
slow_querytable #13129:Prewrite_timeCommit_timeGet_commit_ts_timeCommit_backoff_timeBackoff_typesResolve_lock_timeLocal_latch_wait_timeWrite_keyWrite_sizePrewrite_regionTxn_retry
- Fix the issue that a subquery contained in an
UPDATEstatement is incorrectly converted; fix theUPDATEexecution failure when theWHEREclause contains a subquery #13120 - Support executing
ADMIN CHECK TABLEon partitioned tables #13143 - Fix the issue that the precision of statements such as
SHOW CREATE TABLEis incomplete whenON UPDATE CURRENT_TIMESTAMPis used as a column attribute and floating point precision is specified #12462 - Fix the panic occurred when executing the
SELECT * FROM information_schema.KEY_COLUMN_USAGEstatement because the foreign key is not checked when dropping, modifying or changing the column #14162 - Fix the issue that the returned data might be duplicated when
Streamingis enabled in TiDB #13255 - Fix the
Invalid time formaterror caused by daylight saving time #13624 - Fix the issue that data is incorrect because the precision is lost when an integer is converted to an unsigned floating point or decimal type #13756
- Fix the issue that an incorrect type of value is returned when the
Quotefunction handles theNULLvalue #13681 - Fix the issue that the timezone is incorrect after parsing the date from strings using
gotime.Local#13792 - Fix the issue that the result might be incorrect because the
binSearchfunction does not return an error in the implementation ofbuiltinIntervalRealSig#13768 - Fix the issue that an error might occur when converting the string type to the floating point type in the
INSERTstatement execution #14009 - Fix the incorrect result returned from the
sum(distinct)function #13041 - Fix the issue that
data too longis returned whenCASTconverting the data inunionof the same location to the merged type because the returned type length of thejsonUnquoteFunctionfunction is given an incorrect value #13645 - Fix the issue that the password cannot be set because the privilege check is too strict #13805
- Fix the precision overflow when using
- Server
- Fix the issue that
KILL CONNECTIONmight cause the goroutine leak #13252 - Support getting the binlog status of all TiDB nodes via the
info/allinterface of the HTTP API #13188 - Fix the failure to build the TiDB project on Windows #13650
- Add the
server-versionconfiguration item to control and modify the version of TiDB server #13904 - Fix the issue that the binary
plugincompiled with Go1.13 does not run normally #13527
- Fix the issue that
- DDL
- Use the table’s
COLLATEinstead of the system’s default charset in the column when a table is created and the table containsCOLLATE#13190 - Limit the length of the index name when creating a table #13311
- Fix the issue that the length of the table name is not checked when renaming a table #13345
- Check the width range of the
BITcolumn #13511 - Make the error information output from
change/modify columnmore understandable #13798 - Fix the issue that when executing the
drop columnoperation that has not yet been handled by the downstream Drainer, the downstream might receive DML operations without the affected column #13974
- Use the table’s
TiKV
- Raftstore
- Fix the panic occurred when restarting TiKV and
is_mergingis given an incorrect value in the process of merging Regions and applying the Compact log #5884
- Fix the panic occurred when restarting TiKV and
- Importer
- Remove the limit on the gRPC message length #5809
PD
- Improve the performance of the HTTP API for getting all Regions #1988
- Upgrade etcd to fix the issue that etcd PreVote cannot elect a leader (downgrade not supported) #2052
Tools
- TiDB Binlog
- Optimize the node status information output through binlogctl #777
- Fix the panic occurred because of the
nilvalue in the Drainer filter configuration #802 - Optimize the
Gracefulexit of Pump #825 - Add more detailed monitoring metrics when Pump writes binlog data #830
- Optimize Drainer’s logic to refresh table information after Drainer has executed a DDL operation #836
- Fix the issue that the commit binlog of a DDL operation is ignored when Pump does not receive this binlog #855
TiDB Ansible
Was this page helpful?