tidb v3.1.0-rc Release Notes
Release Date: 2020-04-02 // almost 4 years ago-
๐ New Features
- ๐ Use the binary search to re-implement partition pruning for better performance #15678
- ๐ Support using the
RECOVER
syntax to recover the truncated table #15460 - โ Add
AUTO_RANDOM
ID cache for retrying statement and recovering table #15393 - ๐ Support restoring the state of the
AUTO_RANDOM
ID allocator using therecover table
statement #15393 - ๐ Support
YEAR
,MONTH
, andTO_DAY
functions as the partitioning keys of the Hash partitioned table #15619 - โ Add the table ID to the schema-change related tables only when keys need to be locked in the
SELECT... FOR UPDATE
statement #15708 - โ Add the feature of automatically reading data from different roles according to the load balancing policy and add the leader-and-follower system variable to enable this feature #15721
- ๐ Support dynamically updating the TLS certificate every time TiDB establishes a new connection to update expired client certificate without restarting the RPC client side #15163
- โฌ๏ธ Upgrade PD Client to support loading the latest certificate every time TiDB establishes a new connection #15425
- ๐ง Forcibly use the HTTPS protocol with the configured TLS certificates between a TiDB server and a PD server, or between two TiDB servers when
cluster-ssl-*
is configured #15430 - โ Add the MySQL-compatible
--require-secure-transport
startup option to force the client to enable TLS authentication during the configuration #15442 - โ Add the
cluster-verify-cn
configuration item. After configuration, the status service can only be used when with the corresponding CN certificate #15137
๐ Bug Fixes
- ๐ Use the binary search to re-implement partition pruning for better performance #15678
- ๐ Fix the information schema error caused by frequently updating the TiFlash replica #14884
- Fix the issue that
last_insert_id
is incorrectly generated when applyingAUTO_RANDOM
#15149 * Fix the issue that updating the status of TiFlash replica might cause the DDL operation to get stuck #15161 * ForbidAggregation
pushdown andTopN
pushdown when there are predicates that can not be pushed down #15141 - Forbid the nested
view
creation #15440 - ๐ Fix the error occurred when executing
SELECT CURRENT_ROLE()
afterSET ROLE ALL
#15570 - Fix the failure to identify the
view
name when executing theselect view_name.col_name from view_name
statement #15573 - ๐ Fix the issue that an error might occur when pre-processing DDL statements during the write of binlog information #15444
- ๐ Fix the panic occurred when accessing both
view
s and partitioned tables #15560 - ๐ Fix the error occurred when executing the
VALUES
function with theupdate duplicate key
statement that contains thebit(n)
data type #15487 - ๐ Fix the issue that the specified maximum execution time fails to take effect in some scenarios #15616
- ๐ Fix the issue that fails to check whether the current ReadEngine contains TiKV server when generating the execution plan using
Index Scan
#15773