pingcap/tidb v5.0.2

tidb-server v5.0.2

on GitHub

Improvements

• Avoid frequently reading the mysql.stats_histograms table if the cached statistics is up-to-date to avoid high CPU usage #24317

Bug Fixes

• Fix the panic issue caused by using the prefix index and index join in some cases #24547 #24716 #24717
• Fix the issue that the prepared plan cache of point get is incorrectly used by the point get statement in the transaction #24741
• Fix the issue of writing the wrong prefix index value when the collation is ascii_bin or latin1_bin #24569
• Fix the issue that the ongoing transaction might be interrupted by the GC worker #24591
• Fix a bug that the point query might get wrong on the clustered index when new-collation is enabled but new-row-format is disabled #24541
• Refactor the conversion of partition keys for shuffle hash join #24490
• Fix the panic issue that occurs when building the plan for queries that contain the HAVING clause #24045
• Fix the issue that the column pruning improvement causes the Apply and Join operators' results to go wrong #23887
• Fix a bug that the primary lock fallen back from async commit cannot be resolved #24384
• Fix a GC issue of statistics that might cause duplicated fm-sketch records #24357
• Avoid unnecessary pessimistic rollback when the pessimistic locking receives the ErrKeyExists error #23799
• Fix the issue that numeric literals cannot be recognized when the sql_mode contains ANSI_QUOTES #24522
• Forbid statements such as INSERT INTO table PARTITION (<partitions>) ... ON DUPLICATE KEY UPDATE to read data from non-listed partitions #24746
• Fix the potential index out of range error when a SQL statement contains both GROUP BY and UNION #24281
• Fix the issue that the CONCAT function incorrectly handles the collation #24296
• Fix the issue that the collation_server global variable does not take effect in new sessions #24156