TiDB 3.0.20 Release Notes
Release date: December 25, 2020
TiDB version: 3.0.20
Compatibility Change
TiDB
- Deprecate the
enable-streamingconfiguration item #21054
- Deprecate the
Improvements
TiDB
- Raise an error when preparing the
LOAD DATAstatement #21222
- Raise an error when preparing the
TiKV
- Add the
end_point_slow_log_thresholdconfiguration item #9145
- Add the
Bug Fixes
TiDB
- Fix the incorrect cache of the transaction status for pessimistic transactions #21706
- Fix the issue of inaccurate statistics that occurs when querying
INFORMATION_SCHEMA.TIDB_HOT_REGIONS#21319 - Fix the issue that
DELETEmight not delete data correctly when the database name is not in a pure lower representation #21205 - Fix the issue of stack overflow that occurs when building the recursive view #21000
- Fix the issue of goroutine leak in TiKV client #20863
- Fix the wrong default zero value for the
yeartype #20828 - Fix the issue of goroutine leak in index lookup join #20791
- Fix the issue that executing
INSERT SELECT FOR UPDATEreturns the malformed packet in the pessimistic transaction #20681 - Fix the unknown time zone
'posixrules'#20605 - Fix the issue that occurs when converting the unsigned integer type to the bit type #20362
- Fix the corrupted default value of the bit type column #20339
- Fix the potentially incorrect results when one of the equal condition is the
EnumorSettype #20296 - Fix a wrong behavior of
!= any()#20061 - Fix the issue that type conversion in
BETWEEN...AND...returns invalid results #21503 - Fix a compatibility issue with the
ADDDATEfunction #21008 - Set the correct default value for newly added
Enumcolumn #20999 - Fix the result of SQL statements like
SELECT DATE_ADD('2007-03-28 22:08:28',INTERVAL "-2.-2" SECOND)to be compatible with MySQL #20627 - Fix the incorrect default value when modifying the column type #20532
- Fix the issue that the
timestampfunction gets wrong result when the input argument is thefloatordecimaltype #20469 - Fix a potential deadlock issue in statistics #20424
- Fix the issue that the overflown float type data is inserted #20251
TiKV
- Fix the issue that an error is returned indicating that a key exists when this key is locked and deleted in a committed transaction #8931
PD
- Fix the issue that too many logs are printed when starting PD and when there are too many stale Regions #3064