tidb v4.0.3 Release Notes
Release Date: 2020-07-24 // over 3 years ago-
๐ Improvements
- ๐ฒ Add the
tidb_log_desensitization
global variable to control whether to do desensitization when logging SQL queries #18581 - ๐ Enable
tidb_allow_batch_cop
by default #18552 - Speed up canceling a query #18505
- Add a header for the
tidb_decode_plan
result #18501 - ๐ง Make the configuration checker compatible with earlier versions of the configuration file #18046
- 0๏ธโฃ Enable collecting the execution information by default #18518
- Add the
tiflash_tables
andtiflash_segments
system tables #18536 - ๐ Move
AUTO RANDOM
out of experimental features and announce its general availability. The improvements and compatibility changes are as follows: - ๐ง Deprecate
experimental.allow-auto-random
in the configuration file. No matter how this item is configured, you can always define theAUTO RANDOM
feature on columns. #18613 #18623 - ๐ Add the
tidb_allow_auto_random_explicit_insert
session variable to control the explicit writes onAUTO RANDOM
columns. The default value isfalse
. This is to avoid the unexpectedAUTO_RANDOM_BASE
update caused by explicit writes on columns. #18508 - ๐ Allow defining
AUTO_RANDOM
only onBIGINT
andUNSIGNED BIGINT
columns and restrict the maximum number of shard bits to15
, which avoids the allocatable space being consumed too quickly #18538 - Do not trigger the
AUTO_RANDOM_BASE
update when defining theAUTO_RANDOM
attribute on theBIGINT
column and inserting the negative value into the primary key #17987 - ๐ Use the highest bit of an integer for ID allocation when defining the
AUTO_RANDOM
attribute onUNSIGNED BIGINT
columns, which gets more allocable space #18404 - ๐ Support updating the
AUTO_RANDOM
attribute in the result ofSHOW CREATE TABLE
#18316
๐ Bug Fixes
- Return an error instead of an empty set for
IndexHashJoin
when an error occurs during execution #18586 - ๐ Fix the recurring panic when gRPC transportReader is broken #18562
- ๐ Fix the issue that Green GC does not scan locks on offline stores which might cause data incompleteness #18550
- Forbid processing a non-read-only statement using TiFlash engine #18534
- Return the actual error message when a query connection panics #18500
- ๐ Fix the issue that the
ADMIN REPAIR TABLE
execution fails to reload the table metadata on the TiDB node #18323 - ๐ Fix the data inconsistency issue occurred because the lock of a written and deleted primary key in one transaction is resolved by another transaction #18291
- ๐ Make spilling disk work well #18288
- ๐ Fix the error reported when the
REPLACE INTO
statement works on the table that contains generated columns #17907 - ๐ท Return the OOM error when the
IndexHashJoin
andIndexMergeJoin
workers panic #18527 - ๐ Fix the bug that the execution of
Index Join
might return wrong results in special cases when the index used byIndex Join
contains the integer primary key #18565 - ๐ Fix the issue that when the new collation is enabled on the cluster, the data updated on columns with the new collation in a transaction cannot be read through the unique index #18703
- ๐ฒ Add the