pingcap/tidb v4.0.8

tidb-server v4.0.8

on GitHub

New Features

• Support the new aggregate function APPROX_PERCENTILE #20197

Improvements

• Prioritize low-selectivity indexes in the greedy search procedure of Selectivity() #20154
• Record more RPC runtime information in Coprocessor runtime statistics #19264
• Speed up parsing the slow log to improve query performance #20556
• Wait for timeout execution plans during the plan binding stage to record more debug information when the SQL optimizer is verifying potential new plans #20530
• Add the execution retry time in the slow log and the slow query result #20495 #20494
• Add the table_storage_stats system table #20431
• Add the RPC runtime statistical information for the INSERT/UPDATE/REPLACE statement #20430
• Add the operator information in the result of EXPLAIN FOR CONNECTION #20384
• Adjust the TiDB error log to the DEBUG level for the client connection/disconnection activities #20321
• Add monitoring metrics for Coprocessor Cache #20293
• Add the runtime information of pessimistic lock keys #20199
• Add two extra sections of time consumption information in the runtime information and trace span #20187
• Add the runtime information of transaction commit in the slow log #20185
• Disable the index merge join #20599
• Add the ISO 8601 and timezone supports for temporal string literals #20670

Bug Fixes

• Fix the unexpected panic that occurs when using partitioned tables #20565
• Fix the wrong result of outer join when filtering the outer side using index merge join #20427
• Fix the issue that the NULL value is returned when converting data to the BIT type if the data is too long #20363
• Fix the corrupted default value for the BIT type column #20340
• Fix the overflow error that might occur when converting the BIT type to the INT64 type #20312
• Fix the possible wrong result of the propagate column optimization for the hybrid type column #20297
• Fix the panic that might occur when storing outdated plans from the plan cache #20246
• Fix the bug that the returned result is mistakenly truncated if FROM_UNIXTIME and UNION ALL are used together #20240
• Fix the issue that wrong results might be returned when the Enum type value is converted to the Float type #20235
• Fix the possible panic of RegionStore.accessStore #20210
• Fix the wrong result returned when sorting the maximum unsigned integer in BatchPointGet #20205
• Fix the bug that the coercibilities of Enum and Set are wrong #20364
• Fix an issue of ambiguous YEAR conversion #20292
• Fix the issue of wrong reported result that occurs when the KV duration panel contains store0 #20260
• Fix the issue that the Float type data is mistakenly inserted regardless of the out of range error #20252
• Fix the bug that the generated column does not handle bad NULL values #20216
• Fix the inaccurate error information for the YEAR type data that is out of range #20170
• Fix the unexpected invalid auto-id error that might occur during the pessimistic transaction retry #20134
• Fix the issue that the constraint is not checked when using ALTER TABLE to change the Enum/Set type #20046
• Fix the wrong runtime information of cop tasks recorded when multiple operators are used for concurrency #19947
• Fix the issue that read-only system variables cannot be explicitly selected as the session variables #19944
• Fix the issue that the duplicate ORDER BY condition might cause sub-optimal execution plans #20333
• Fix the issue that the generated metric profile might fail if the font size exceeds the maximum allowable value #20637