TiDB - v5.3.2

Compatibility Changes

• Fix the issue that the REPLACE statement incorrectly changes other rows when the auto ID is out of range #29483

Bug Fixes

• Fix the issue that Amazon S3 cannot correctly calculate the size of compressed data #30534
• Fix the issue of potential data index inconsistency in optimistic transaction mode #30410
• Fix the issue that a SQL operation is canceled when its JSON type column joins its CHAR type column #29401
• Previously, when a network connectivity issue occurred, TiDB did not always correctly free the resources held by the disconnected session. This issue has been fixed so that open transactions can be rolled back and other associated resources can be released. #34722
• Fix the issue of the data and columnID count not match error that occurs when inserting duplicated values with TiDB Binlog enabled #33608
• Fix the issue that query result might be wrong when Plan Cache is started in the RC isolation level #34447
• Fix the session panic that occurs when executing the prepared statement after table schema change with the MySQL binary protocol #33509
• Fix the issue that the table attributes are not indexed when a new partition is added and the issue that the table range information is not updated when the partition changes #33929
• Fix the issue that the TiDB server might run out of memory when the INFORMATION_SCHEMA.CLUSTER_SLOW_QUERY table is queried. This issue can be triggered when you check slow queries on the Grafana dashboard #33893
• Fix the issue that some DDL statements might be stuck for a period after the PD node of a cluster is replaced #33908
• Fix the issue that granting the all privilege might fail in clusters that are upgraded from v4.0 #33588
• Fix wrong results of deleting data of multiple tables using left join #31321
• Fix a bug that TiDB may dispatch duplicate tasks to TiFlash #32814
• Fix the issue that the background HTTP service of TiDB might not exit successfully and makes the cluster in an abnormal state #30571
• Fix the panic issue caused by the fatal error: concurrent map read and map write error #35340