TiDB 4.0.0-beta has been released, this version updates are as follows:
Improvements
Index Join
By considering the number of rows in the table-driven table and driven to improve the accuracy of calculation cost # 12085- When the index can completely cover the columns involved in the query, improve performance # 12022
- By supporting the index merge feature # 10121 # 10512 # 11245 # 122,248 # 12248 # 12305 # 12305 # 12305 # 12248 # 12248 # 12305 # 12305 # 12248 # 12305 # 12305 # 12248 # 12248 # 12248 # 12305
- By the results and eliminate duplicate cache index result, improve performance and reduce the range of the calculated CPU overhead # 12856
- The level and ordinary level slow log log isolated # 12359
- The
query-log-max-len
default value of the parameter is increased to4096
reduce the number of SQL truncated output. This parameter can be dynamically adjusted. # 12491 - ......
New Features
- Support in
ADMIN SHOW DDL JOBS
useLIKE
orWHERE
clause condition filter # 12484 - In
information_schema.tables
adding tableTIDB_ROW_ID_SHARDING_INFO
columns to outputRowID
the scattered information (e.g., the tableA
ofSHARD_ROW_ID_BITS
value"SHARD_BITS={bit_number}"
) # 13418 - Add
oom-use-tmp-storage
parameters (by defaulttrue
) to control when performing memory usage exceeds a single SQL statementmem-quota-query
and contains SQLHash Join
, the temporary files to cache whether the intermediate results # 11832 # 11937 # 12116 # 12067 - By HTTP support
info/all
binlog status query interface to the cluster-enabled server TiDB # 13025 - Add support column attribute
AutoRandom
keywords to whether the control system is automatically assigned to the primary key a random integer, thereby avoiding theAUTO_INCREMENT
hot spots caused by the primary key # 13127 - Support Locks the Table # 11038
- ......
Changed Behaviors
- Error Code SQL optimization to eliminate the error message
ERROR 1105 (HY000)
codes (Unknown Error
type) - When performing
INSERT
/REPLACE
/DELETE
/UPDATE
used during memory thanMemQuotaQuery
the specified limit entry configuration, log or cancel print SQL execution. The actual behavior depends onOOMAction
the configuration # 14179 # 14289 # 14299
Bugfix
- Repair and RBAC several issues related to # 13820 # 13940 # 14090 # 13940 # 13014
- Since the restoration
SELECT
statement containsunion
issues and can not create a VIEW # 12595 - Repair and
CAST
several issues related to the function
More details to see the release notes .