RATATOSK
← All releases

TiKVv8.5.4

Breaking changes 5Deprecations 1Important fixes 42Enhancements 11Dependency updates 1Other changes 50

Get TiKV alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Prerequisites2
Smooth upgrades from newly created v8.5.3 clusters

This release changes defaults and behavior for system variables and configuration parameters.

Newly created v8.5.3 clusters can be smoothly upgraded to v8.5.4. However, v8.5.4 introduces several default value changes and behavior adjustments for system variables and configuration parameters. Before upgrading, pay attention to the following:
docs.pingcap.com/tidb/stable/release-8.5.4
Upgrade guidance for customized TiFlash and TiKV compaction configurations

Most changes are safe for routine upgrades; clusters with these custom configurations need careful review.

- Most changes are safe for routine upgrades. However, if your cluster has undergone performance tuning, such as customized TiFlash and TiKV compaction configurations, read this section carefully.
docs.pingcap.com/tidb/stable/release-8.5.4

Breaking changes5

tidb_replica_read limited to read-only SQL

AffectsSQL statements using tidb_replica_read(Inferred)
Show release-note lines
tidb_replica_read Modified Starting from v8.5.4, this variable only takes effect on read-only SQL statements. This improves data read safety and reduces overlaps with other features. #62856 @you06
docs.pingcap.com/tidb/stable/release-8.5.4

CPU-based default for server.grpc-raft-conn-num

AffectsTiKV setups using the default for server.grpc-raft-conn-num

Previously, the default was 1; it now follows MAX(1, MIN(4, CPU cores / 8)), adapting the connection count to CPU core count.

Show release-note lines
TiKV server.grpc-raft-conn-num Modified Changes the default value from 1 to MAX(1, MIN(4, CPU cores / 8)) , which enables gRPC-related thread settings to adapt to the number of CPU cores. When the number of CPU cores equals or exceeds 32, the maximum default number of connections is 4. #18806 @LykxSassinator
docs.pingcap.com/tidb/stable/release-8.5.4

TiKV changes the server.grpc-concurrency default

AffectsTiKV setups using the default for server.grpc-concurrency

The default was 5; setups still using it now get grpc-raft-conn-num * 3 + 2 instead, adapting gRPC-related thread settings to the number of CPU cores.

Show release-note lines
TiKV server.grpc-concurrency Modified Changes the default value from 5 to grpc-raft-conn-num * 3 + 2 , which enables gRPC-related thread settings to adapt to the number of CPU cores. #18806 @LykxSassinator
docs.pingcap.com/tidb/stable/release-8.5.4

max_execution_time enforcement fixed for SELECT FOR UPDATE statements

Affectssetups with max_execution_time configured for SELECT FOR UPDATE statements

Before this fix, max_execution_time did not take effect when a SELECT FOR UPDATE statement ran.

Show release-note lines
- Fix the issue that max_execution_time does not take effect for SELECT FOR UPDATE statements #62960 @ ekexium
docs.pingcap.com/tidb/stable/release-8.5.4

Bucket splitting stops when bucket reporting is disabled

Affectssetups with bucket reporting disabled and bucket splitting in use(Inferred)

Before this fix, bucket splitting still worked when bucket reporting was disabled.

Show release-note lines
- Fix the issue that splitting buckets still works even after bucket reporting is disabled #9726 @ bufferflies
docs.pingcap.com/tidb/stable/release-8.5.4

Deprecations1

TiKV automatic-compaction settings replaced by gc.auto-compaction

AffectsTiKV configurations using the region-compact-* items or gc.auto-compaction settings(Inferred)
Removed innot stated

The region-compact-* items were the existing settings for this behavior; the new group controls automatic compaction.

Show release-note lines
TiKV - region-compact-check-interval
- region-compact-check-step
- region-compact-min-tombstones
- region-compact-tombstones-percent
- region-compact-min-redundant-rows
- region-compact-redundant-rows-percent
Deprecated These configuration items are replaced by the gc.auto-compaction configuration group, which controls the automatic compaction behavior. #18727 @v01dstar
TiKV gc.auto-compaction configuration group: - gc.auto-compaction.check-interval
- gc.auto-compaction.tombstone-num-threshold
- gc.auto-compaction.tombstone-percent-threshold
- gc.auto-compaction.redundant-rows-threshold
- gc.auto-compaction.redundant-rows-percent-threshold
- gc.auto-compaction.bottommost-level-force
Newly added This configuration group controls the automatic compaction behavior. #18727 @v01dstar
docs.pingcap.com/tidb/stable/release-8.5.4

Important fixes42Silent failure4

  • Row count overestimation corrected for long spans
    Affectsrow count estimates spanning months or years

    Those estimates could be significantly too high.

    - Fix the issue that row count estimates across months or years can be significantly overestimated #50080 @ terry1purcell
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect regular-expression query results fixed for INFORMATION_SCHEMA
    AffectsINFORMATION_SCHEMA queries

    Queries using regular expressions against INFORMATION_SCHEMA tables might return incorrect results.

    - Fix the issue that queries using regular expressions against INFORMATION_SCHEMA tables might return incorrect results #62347 @ River2000i
    docs.pingcap.com/tidb/stable/release-8.5.4
  • ADMIN ALTER DDL JOBS parameter display fixed
    Affectssetups that dynamically modify parameters and use ADMIN ALTER DDL JOBS statements

    After parameters were dynamically modified, ADMIN ALTER DDL JOBS statements displayed incorrect parameter values.

    - Fix the issue that ADMIN ALTER DDL JOBS statements display incorrect parameter values after dynamically modifying parameters #63201 @ fzzf678
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect ATAN2 results fixed
    Affectsqueries using the ATAN2 function

    Using ATAN2 could produce incorrect results; this release fixes that behavior.

    - Fix the issue that using the ATAN2 function might produce incorrect results #60093 @ guo-shaoge
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Variable restoration after set_var hints with bindings fixed
    Affectsbindings using the set_var hint

    When the set_var hint was used with bindings, variables could remain unrestored and keep settings other than their original values. They are now restored to their original settings in this case.

    - Fix the issue that using the set_var hint with bindings prevents variables from being restored to their original settings #59822 @ wddevries
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect results from outer-to-inner join rewrites fixedSilent failure
    Affectsqueries using outer-to-inner join rewrites

    When an outer join was rewritten to an inner join, the rewrite could produce incorrect results. This release fixes those results.

    - Fix the issue that rewriting an outer join to an inner join might produce incorrect results #61327 @ hawkingrei
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect global-index results fixedSilent failure
    Affectssetups using global indexes

    In some cases, the global index could return incorrect results. Those incorrect results are fixed in this release.

    - Fix the issue that the global index might return incorrect results in some cases #61083 @ Defined2014
    docs.pingcap.com/tidb/stable/release-8.5.4
  • character_set_results character replacement fixedSilent failure
    Affectssetups using character_set_results

    Previously, affected characters were truncated instead of replaced. They are now replaced rather than truncated.

    - Fix the issue that character_set_results truncates incorrect characters instead of replacing them #61085 @ xhebox
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect TSO HTTP API results fixed
    Affectssetups using the TSO HTTP API /config or /members endpoints

    Before this release, these endpoints returned incorrect results.

    - Fix the issue that the TSO HTTP API /config and /members return incorrect results #9797 @ lhy1024
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiFlash RU-consumption statistics inflation fixed
    AffectsTiFlash setups that generate statistics for RU consumption(Inferred)

    When TiFlash generated statistics for RU consumption, the reported values were inflated.

    - Fix the issue that TiFlash generates inflated statistics for RU consumption #10380 @ JinheLin
    docs.pingcap.com/tidb/stable/release-8.5.4
  • FLOOR() and CEIL() DECIMAL results fixedSilent failure
    AffectsTiFlash setups using FLOOR() or CEIL() with DECIMAL parameters

    When called with a DECIMAL parameter, these functions could return incorrect results; they now return corrected results.

    - Fix the issue that the FLOOR() and CEIL() functions might return incorrect results when their parameters are of the DECIMAL type #10365 @ ChangRui-Ryan
    docs.pingcap.com/tidb/stable/release-8.5.4
  • mysql.stats_meta count restoration fixed
    Affectsbackups made with --checksum set to false

    After restore, the count column in mysql.stats_meta could become 0. This issue is fixed in this release.

    - Fix the issue that setting --checksum to false during backup might cause the count column in the mysql.stats_meta table to become 0 after restore #60978 @ Leavrth
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Log backup zstd compression restored
    AffectsTiKV setups using log backup with the default zstd fastest setting

    When log backup used the default algorithm expected to be zstd fastest, async-compression v0.4.12's negative default level disabled or made zstd compression ineffective.

    - tikv/tikv#18836
    - Fix the issue that zstd compression in log backup does not take effect, causing the output to remain uncompressed #18836 @ 3pointer
    github.com/tikv/tikv/releases/tag/v8.5.4
  • Azure Blob backup flush slowdown fixed
    Affectssetups backing up to Azure Blob storage with uploads reading from a non-memory source

    During backups to Azure Blob Storage, a 400 MiB flush could take about 17 minutes and use a full CPU core.

    - tikv/tikv#18410
    - Fix the issue that the flush operation occasionally becomes slow when backing up data to Azure Blob Storage #18410 @ YuJuncen
    github.com/tikv/tikv/releases/tag/v8.5.4
  • Compaction scoring uses GC safe points
    AffectsTiKV setups that calculate compaction scores in relation to the GC safe point(Inferred)

    MVCC redundancy is calculated using GC safe points and RocksDB statistics, improving the efficiency and accuracy of compaction scoring.

    - tikv/tikv#18697
    - Calculate MVCC redundancy based on GC safe points and RocksDB statistics to improve the efficiency and accuracy of compaction #18697 @ v01dstar
    github.com/tikv/tikv/releases/tag/v8.5.4
  • Log backup region observation loss fixed
    Affectslog backup setups

    When a region became leader while a new log backup task was initializing, reordered Start and Stop observe messages could leave it unobserved, causing progress to stop advancing with a stale observe ID error. The observer now retains observation of the region in this situation.

    - tikv/tikv#18243
    - Fix the issue that log backup observer might lose the observation on a Region, causing the log backup progress to fail to advance #18243 @ Leavrth
    github.com/tikv/tikv/releases/tag/v8.5.4
  • TiKV CDC assertion panic fixed
    Affectssetups using TiKV CDC

    On TiKV v8.5.1, a CDC processing path could hit an assertion with mismatched timestamps, which could cause TiCDC to panic.

    - tikv/tikv#18498
    - Fix the issue that assertion errors in TiKV might cause TiCDC to panic #18498 @ tharanga
    github.com/tikv/tikv/releases/tag/v8.5.4
  • CDC region-subscription panic fixed
    Affectssetups using CDC

    CDC could theoretically panic if a region was subscribed between a key rollback and the prewrite entry; the issue report said this had not occurred in reality.

    - tikv/tikv#19048
    - Fix the issue that TiCDC might panic when encountering rollback and prewrite entries during Region subscription #19048 @ 3AceShowHand
    github.com/tikv/tikv/releases/tag/v8.5.4
  • ANALYZE support for index-related DDL
    AffectsTiDB setups with tidb_stats_update_during_ddl enabled

    TiDB runs ANALYZE before a new or reorganized index becomes visible, helping avoid inaccurate optimizer estimates and plan changes while statistics are unavailable. The variable is OFF by default, and enabling it can increase ADD INDEX execution time on large tables.

    - Support ANALYZE embedded in DDL statements #57948 @ terry1purcell @ AilinKid
    This feature applies to the following types of DDL statements:
    - DDL statements that create new indexes: ADD INDEX
    - DDL statements that reorganize existing indexes: MODIFY COLUMN and CHANGE COLUMN
    When this feature is enabled, TiDB automatically runs an ANALYZE (statistics collection) operation before the new or reorganized index becomes visible to users. This prevents inaccurate optimizer estimates and potential plan changes caused by temporarily unavailable statistics after index creation or reorganization.
    For more information, see documentation .
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Automatically recoverable BR backup errors logged at WARN
    AffectsBR backup operations

    During conditions such as backup snapshot failed and backup writer failed, these automatically recoverable errors were previously logged at ERROR despite not being error-level conditions and requiring manual operation.

    - Change the log level of certain automatically recoverable errors in the BR module from ERROR to WARN to reduce unnecessary alerts #18493 @ YuJuncen
    - tikv/tikv#18493
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Certain TiKV errors logged at WARN
    AffectsTiKV setups that emit the affected errors

    When these errors occur, they were previously logged at ERROR; logging them at WARN reduces unnecessary alerts.

    - Change the log level of certain TiKV errors from ERROR to WARN to reduce unnecessary alerts #18745 @ exit-code-1
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect short-path processing in TRUNCATE() fixed
    Affectsqueries that use the short path in TRUNCATE()(Inferred)
    - Fix the issue that the short path in the TRUNCATE() function is incorrectly processed #57608 @ xzhangxian1008
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Spilled-file cleanup fixed for local temporary space quota errors
    Affectssetups that spill files

    When the Out Of Quota For Local Temporary Space error was triggered, spilled files might not be fully deleted.

    - Fix the issue that spilled files might not be fully deleted when the Out Of Quota For Local Temporary Space error is triggered #63216 @ xzhangxian1008
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiDB error reporting for failed PD timestamp retrieval fixed
    AffectsTiDB setups that get timestamps from PD

    Previously, when TiDB failed to get a timestamp from PD, it did not return an error.

    - Fix the issue that TiDB does not return an error when it fails to get a timestamp from PD #58871 @ joechenrh
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Owner and non-owner TiDB query result mismatch fixed for MODIFY COLUMN
    AffectsMODIFY COLUMN statements across owner and non-owner TiDB instances

    During MODIFY COLUMN statements, query results differed between owner and non-owner TiDB instances.

    - Fix the issue that query results differ between the owner TiDB and non-owner TiDB instances during executing MODIFY COLUMN statements #60264 @ tangenta
    docs.pingcap.com/tidb/stable/release-8.5.4
  • GC safe point advancement fixed for index creation in transactions
    Affectstransactions that add an index

    The GC safe point did not advance when an index was added within a transaction.

    - Fix the issue that the GC safe point does not advance when adding an index within a transaction #62424 @ wjhuang2016
    docs.pingcap.com/tidb/stable/release-8.5.4
  • DXF task cancellation exit failure fixed
    Affectssetups using DXF

    When a DXF task was canceled while other tasks were running, those tasks failed to exit.

    - Fix the issue that after the DXF task is canceled, other tasks fail to exit #63927 @ D3Hunter
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Apply operator plan generation failure fixed
    Affectssetups with Apply operator concurrency enabled using tidb_enable_parallel_apply = on

    With tidb_enable_parallel_apply = on, plan generation failed because the Apply operator concurrency path was missing a clone implementation.

    - Fix the issue that enabling the Apply operator concurrency ( tidb_enable_parallel_apply = on ) causes plan generation failure due to a missing clone implementation #59863 @ hawkingrei
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Case-insensitive behavior of the ONLY_FULL_GROUP_BY check fixed
    AffectsThe ONLY_FULL_GROUP_BY check(Inferred)

    When the check handled inputs whose behavior depended on case, it treated them case-insensitively. That behavior is fixed, but the note does not specify the replacement behavior.

    - Fix the issue that the ONLY_FULL_GROUP_BY check is case-insensitive #62672 @ AilinKid
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Internal panic on certain queries fixed
    Affectssetups that execute the affected queries

    Executing certain queries could trigger an internal panic; the note does not identify which queries.

    - Fix the issue that executing certain queries might cause an internal panic #58600 @ Defined2014
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Incorrect global-index reads during ALTER PARTITION fixed
    Affectssetups using global indexes and performing ALTER PARTITION operations

    During certain ALTER PARTITION operations, the global index could return incorrect data. Those reads are fixed in this release.

    - Fix the issue that the global index might read incorrect data during certain ALTER PARTITION operations #64084 @ mjonss
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Resource Manager token allocation fix
    Affectssetups using the Resource Manager(Inferred)

    When the Resource Manager incorrectly allocated tokens, queries could get stuck.

    - Fix the issue that the Resource Manager incorrectly allocates tokens, causing queries to be stuck #9455 @ JmPotato
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Placement Rules after PD leader switches fixed
    Affectssetups using Placement Rules

    When the PD leader switched, Placement Rules did not take effect.

    - Fix the issue that Placement Rules do not take effect after PD leader switches #9602 @ okJiang
    docs.pingcap.com/tidb/stable/release-8.5.4
  • PD parsing of large scientific-notation values fixed
    AffectsTTL-related configurations containing large numeric values in scientific notation

    When PD encountered large numeric values in scientific notation, it could fail to parse them, so some TTL-related configurations did not take effect.

    - Fix the issue that PD might fail to parse large numeric values in scientific notation, which consequently causes some TTL-related configurations to not take effect #9343 @ lhy1024
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiFlash out-of-memory condition fixed
    AffectsTiFlash using disaggregated storage and compute

    When slow queries existed, TiFlash could run out of memory. This condition is fixed in this release.

    - Fix the issue that TiFlash might encounter OOM when slow queries exist under the disaggregated storage and compute architecture #10278 @ JaySon-Huang
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiFlash indefinite retries with S3 fixed
    AffectsTiFlash deployments using disaggregated storage and compute with S3

    During a network partition between TiFlash and S3, TiFlash could retry indefinitely. That indefinite-retry behavior is fixed.

    - Fix the issue that TiFlash might retry indefinitely when a network partition occurs between TiFlash and S3 under the disaggregated storage and compute architecture #10424 @ JaySon-Huang
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Log truncation on file-deletion failure fixed
    Affectslog operations involving file deletion(Inferred)

    When file deletion failed, log truncation might occur.

    - Fix the issue that log truncate might occur when file deletion fails #63358 @ YuJuncen
    docs.pingcap.com/tidb/stable/release-8.5.4
  • BR restore failure risk reduced for bandwidth-limited S3-compatible storage
    AffectsS3-compatible storage services with bandwidth limits enabled

    Stalled-stream protection could kill a download request, which could then restart from the beginning and fail with a “streaming error.” This release reduces the chance of that restore failure but does not eliminate it.

    - Reduce the possibility of BR failing to restore data from S3-compatible storage services when the bandwidth limits on these services are enabled #18846 @ kennytm
    - tikv/tikv#18846
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiCDC column-type partition dispatcher panic fixed
    AffectsTiCDC column-type partition dispatchers with virtual columns
    - Fix a panic that could occur when configuring a column-type partition dispatcher that includes virtual columns #12241 @ wk989898
    docs.pingcap.com/tidb/stable/release-8.5.4
  • DDL puller close panic fixed
    AffectsTiCDC setups that close the DDL puller

    Closing the DDL puller could cause a panic; after this release, closing it no longer triggers that panic.

    - Fix a panic that could occur when closing the DDL puller #12244 @ wk989898
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Azure Blob Storage changefeed task stalls fixed
    AffectsTiCDC changefeeds using Azure Blob Storage as the downstream

    Tasks could get stuck in this setup; this release addresses the issue.

    - Fix the issue that changefeed tasks might get stuck when using Azure Blob Storage as the downstream #12277 @ zurakutsia
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiCDC replication of DROP FOREIGN KEY DDL fixed
    AffectsTiCDC setups replicating DDL to a downstream(Inferred)

    When DROP FOREIGN KEY DDL was replicated to a downstream, it was not sent. It is now replicated.

    - Fix the issue that DROP FOREIGN KEY DDL is not replicated to the downstream #12328 @ 3AceShowHand
    docs.pingcap.com/tidb/stable/release-8.5.4

Enhancements11

  • gRPC overload wait-time metrics
  • Per-table distribution inspection and redistribution

    To use v8.5.4 or later

    - Support redistributing data of a specific table (experimental) #63260 @ bufferflies
    PD automatically schedules data to be distributed as evenly as possible across all TiKV nodes in a cluster. However, this automatic scheduling focuses on the cluster as a whole. In some cases, even if the cluster-wide data distribution is balanced, the data of a specific table might still be unevenly distributed across TiKV nodes.
    Starting from v8.5.4, you can use the SHOW TABLE DISTRIBUTION statement to check how the data of a specific table is distributed across all TiKV nodes. If the data distribution is unbalanced, you can use the DISTRIBUTE TABLE statement to redistribute the table's data (experimental) to improve load balancing.
    Note that redistributing the data of a specific table is a one-time task with a timeout limit. If the distribution task is not completed before the timeout, it will automatically exit.
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiDB adds global index support for non-unique columns in partitioned tables

    To use TiDB v8.5.4 or later

    - Support creating global indexes on non-unique columns of partitioned tables #58650 @ Defined2014 @ mjonss
    Starting from v8.3.0, you can create global indexes on unique columns of partitioned tables in TiDB to improve query performance. However, creating global indexes on non-unique columns was not supported. Starting from v8.5.4, TiDB removes this restriction, enabling you to create global indexes on non-unique columns of partitioned tables, which enhances the usability of global indexes.
    For more information, see documentation .
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Optional redesigned TiCDC architecture

    To use Set the TiCDC configuration item newarch to true.

    - Introduce a new TiCDC architecture option for improved performance, scalability, and stability #442 @ CharlesCheung96
    This new architecture redesigns TiCDC core components and optimizes its data processing workflows, while maintaining compatibility with the configuration, usage, and APIs of the classic TiCDC architecture .
    When configured to use this new architecture, TiCDC achieves near-linear scalability and can replicate millions of tables with lower resource consumption. It also reduces changefeed latency and delivers more stable performance in scenarios with high write workloads, frequent DDL operations, and cluster scaling. Note that the new architecture currently has some initial limitations .
    To use the new architecture, set the TiCDC configuration item newarch to true .
    For more information, see documentation .
    docs.pingcap.com/tidb/stable/release-8.5.4
  • SELECT-list subquery decorrelation control variable added
    tidb_opt_enable_no_decorrelate_in_select Newly added Controls whether to decorrelate subqueries in the SELECT list. The default value is OFF . #51116 @terry1purcell
    docs.pingcap.com/tidb/stable/release-8.5.4
  • EXISTS subquery rewrite control variable added
    tidb_opt_enable_semi_join_rewrite Newly added Controls whether to rewrite EXISTS subqueries. The default value is OFF . #44850 @terry1purcell
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Embedded ANALYZE during ADD INDEX
    tidb_stats_update_during_ddl Newly added Controls whether to enable ANALYZE Embedded in DDL Statements . The default value is OFF . When it is enabled, the ADD INDEX DDL statement collects statistics for the new index during execution, allowing the optimizer to use the index immediately after it is added. Note that enabling this variable might increase DDL execution time when adding indexes to large tables. #57948 @terry1purcell @AilinKid
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Support for semi_join_rewrite on Semi Joins in IN subqueries

    To use The semi_join_rewrite hint, applied to Semi Joins in IN subqueries

    - Support applying the semi_join_rewrite hint to Semi Joins in IN subqueries #58829 @ qw4990
    docs.pingcap.com/tidb/stable/release-8.5.4
  • Backoff metric added to the Grafana SQL Execute Time Overview panel
    - Add the backoff metric to the Performance Overview > SQL Execute Time Overview panel in Grafana to facilitate debugging #61441 @ dbsid
    docs.pingcap.com/tidb/stable/release-8.5.4
  • PD table-level Region scattering across scatter-role and engine dimensions
    - Support scattering Regions at the table level to achieve balanced distribution across scatter-role and engine dimensions #8986 @ bufferflies
    docs.pingcap.com/tidb/stable/release-8.5.4
  • TiCDC support for filtering unsupported DDL types

    To use The ignore-txn-start-ts parameter in the filter configuration

    - Support filtering unsupported DDL types through the ignore-txn-start-ts parameter in the filter configuration #12286 @ asddongmen
    docs.pingcap.com/tidb/stable/release-8.5.4

Dependency updates1

    1 more, none mentioning security
    • - Upgrade the Golang version from 1.23.0 to 1.23.12 and update related dependencies #9788 @ JmPotato
    Other changes50
    • Repeated compaction tasks queued to cleanup_worker
    • SST ingestion compatibility guard behavior
    • Titan region-size estimation issue noted
    • IMPORT INTO cleanup failure issue listed
    • Slow Tick(CompactCheck) handling observed
    • Slow reads with the resource-control auto priority limiter
    • Async snapshot tail latency with growing SST-file counts
      - tikv/tikv#18743
      - Optimize the tail latency of async snapshot and write operations in environments with a large number of SST files #18743 @ Connor1996
      github.com/tikv/tikv/releases/tag/v8.5.4
    • BR restore download-failure logging issue
    • Proposed increase to the default RocksDB manifest size
    • Frequent store-size reporting issue recorded
    • SST importer cache deadlock issue noted
    • tikv-cdc assertion panic recorded
    • RawRecords top-N aggregation proposal
    • TiKV RocksDB write crash issue listed
    • Graceful shutdown for TiFlash MPP tasks
      - Support gracefully shutting down TiFlash #10266 @ gengliqi
      When shutting down a TiFlash server, TiFlash now lets currently running MPP tasks continue for a configurable timeout duration, while rejecting new MPP task requests. The default timeout duration is 600 seconds, and you can adjust it using the flash.graceful_wait_shutdown_timeout configuration item.
      - If all running MPP tasks finish before the timeout duration expires, TiFlash shuts down immediately.
      - If there are still unfinished MPP tasks when the timeout duration expires, TiFlash shuts down forcibly.
      For more information, see documentation .
      TiFlash flash.graceful_wait_shutdown_timeout Newly added Controls the maximum wait time (in seconds) for a graceful TiFlash shutdown. The default value is 600 . When shutting down TiFlash, it continues executing unfinished MPP tasks but no longer accepts new MPP tasks. If all MPP tasks finish before the timeout, TiFlash shuts down immediately; otherwise, it is forcibly shut down after the timeout expires. #10266 @gengliqi
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB's default wait before querying new TiFlash nodes removed
      tidb_mpp_store_fail_ttl Modified Changes the default value from 60s to 0s . This means TiDB no longer needs to wait before sending queries to newly started TiFlash nodes, as delays are no longer necessary to prevent query failures. #61826 @gengliqi
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiKV increases the default for rocksdb.max-manifest-file-size
      TiKV rocksdb.max-manifest-file-size Modified Changes the default value from 128MiB to 256MiB to avoid frequent manifest file compactions that could affect overall performance when a single TiKV node contains a large number of SST files. #18889 @glorv
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiCDC adds the scheduler.region-count-per-span table-splitting setting
      TiCDC scheduler.region-count-per-span Newly added Introduced in the TiCDC new architecture . During changefeed initialization, TiCDC splits tables that meet the split conditions according to this parameter. Each split sub-table contains at most region-count-per-span Regions. The default value is 100 .
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB accepts over-scale DECIMAL inserts with truncation
      Starting from v8.5.4, TiDB aligns its behavior with MySQL when inserting data into a DECIMAL column: if the number of decimal places exceeds the column's defined scale, TiDB automatically truncates the extra digits and inserts the truncated data successfully, regardless of how many extra decimal places there are. In earlier TiDB versions, if the number of decimal places in the inserted DECIMAL value exceeded 72, the insertion fails and returns an error. For more information, see Connect to TiDB using JDBC .
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB estimation strategy optimized
      - Optimize the estimation strategy when the tidb_opt_ordering_index_selectivity_ratio system variable takes effect #62817 @ terry1purcell
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB optimizer index-selection logic adjusted
      - Adjust the optimizer selection logic to make newly created indexes more likely to be chosen in certain scenarios #57948 @ terry1purcell
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB query estimation optimized for columns with few distinct values
      - Optimize the query estimation logic for columns with a small number of distinct values (NDV) #61792 @ terry1purcell
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Optimized estimates for TiDB Index Join queries with LIMIT OFFSET
      - Optimize the estimation strategy for Index Join queries that include LIMIT OFFSET #45077 @ qw4990
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB out-of-range estimation optimized
      - Optimize the out-of-range estimation strategy when statistics are not collected in time #58068 @ terry1purcell
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB audit log now includes statement ID information
      - Add statement ID information to the audit log plugin #63525 @ YangKeao
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Raft GC checks split into two phases
      - Split the GC check process in the Raft module into two phases to improve the efficiency of garbage collection for redundant MVCC versions in Regions #18695 @ v01dstar
      - tikv/tikv#18695
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Region MVCC GC handling moved to GC worker threads
      - Change the GC handling logic for Region MVCC to be executed by GC worker threads, unifying the overall GC processing logic #18727 @ v01dstar
      docs.pingcap.com/tidb/stable/release-8.5.4
    • gRPC thread pool size now scales with CPU quota by default
      - Optimize the calculation method of the default gRPC thread pool size by making it dynamically calculated based on total CPU quota instead of a fixed value, avoiding performance bottlenecks caused by insufficient gRPC threads #18613 @ LykxSassinator
      docs.pingcap.com/tidb/stable/release-8.5.4
    • PD emits fewer unnecessary error logs
      - Reduce unnecessary error logs #9370 @ bufferflies
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiFlash skips unnecessary reads during TableScan
      - Skip unnecessary data reads to improve TableScan performance #9875 @ gengliqi
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiFlash TableScan performance optimized for wide, sparse tables
      - Optimize TableScan performance on wide tables with many columns and sparse data (that is, lots of NULL or empty values) in TiFlash #10361 @ JaySon-Huang
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Reduced TiFlash CPU overhead from adding vector indexes
      - Reduce TiFlash CPU overhead caused by adding vector indexes in clusters with many tables #10357 @ Lloyd-Pottiger
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Reduced unnecessary TiFlash logs for useless Raft commands
      - Minimize unnecessary log output when processing useless Raft commands to reduce log volume #10467 @ JaySon-Huang
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiFlash TableScan performance improved on small partitioned tables
      - Improve TableScan performance on small partitioned tables in TiFlash #10487 @ JaySon-Huang
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Case-insensitive upstream GTID_MODE matching in TiDB Data Migration
      - Support case-insensitive matching when retrieving the upstream GTID_MODE #12167 @ OliverS929
      docs.pingcap.com/tidb/stable/release-8.5.4
    • USE INDEX hint failure with TiFlash isolation reads fixed
      - Fix the issue that the use index hint does not take effect when tidb_isolation_read_engines is set to tiflash #60869 @ Lloyd-Pottiger
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiDB Decimal handling in prepared statements fixed
      - Fix the issue that the handling of Decimal types in prepared statements is inconsistent with MySQL #62602 @ ChangRui-Ryan
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Flow control fix for excessively large L0 SST ingestion
      - Fix the issue that ingesting excessively large SST files into L0 triggers flow control #63466 @ CbcWestwolf
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Global sorting fixed for a 1:2 CPU-to-memory ratio
      - Fix the issue that global sorting is blocked when the CPU-to-memory ratio is 1:2 #60951 @ wjhuang2016
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Pending DXF task cancellation fixed
      - Fix the issue that pending Distributed eXecution Framework (DXF) tasks cannot be canceled when the number of tasks exceeds 16 #63896 @ D3Hunter
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Instance-level plan cache enabled for select 1 from dual
      - Fix the issue that select 1 from dual cannot use the instance-level plan cache #63075 @ time-and-fate
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Planner failures when query join order changes fixed
      - Fix the issue that changing the join order might cause the planner to fail #61715 @ hawkingrei
      docs.pingcap.com/tidb/stable/release-8.5.4
    • ONLY_FULL_GROUP_BY negative-value validation failure fixed
      - Fix the issue that setting ONLY_FULL_GROUP_BY to a negative value causes validation failure #62617 @ AilinKid
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Incorrect plans from the DP join order algorithm fixed
      - Fix the issue that the DP join order algorithm might generate an incorrect plan #63353 @ winoros
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Errors from concurrent ADD COLUMN and UPDATE fixed
      - Fix the issue that running ADD COLUMN and UPDATE statements concurrently might cause errors #60047 @ L-maple
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Merge Join filter-condition cost calculation fixed
      - Fix the issue that Merge Join might omit filter conditions when calculating costs #62917 @ qw4990
      docs.pingcap.com/tidb/stable/release-8.5.4
    • PD Client retry strategy initialization fixed
      - Fix the issue that the PD Client retry strategy is not initialized correctly #9013 @ rleungx
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TSO Follower Proxy error handling fixed
      - Fix the incorrect error handling logic of TSO Follower Proxy #9188 @ Tema
      docs.pingcap.com/tidb/stable/release-8.5.4
    • TiFlash query failures fixed
      - Fix the issue that queries might fail when queried columns contain a large number of NULL values #10340 @ Lloyd-Pottiger
      docs.pingcap.com/tidb/stable/release-8.5.4
    • Restore point creation failure with special schemas fixed
      - Fix the issue that causes restore point creation to fail when backed-up tables include certain special schemas #63663 @ RidRisR
      docs.pingcap.com/tidb/stable/release-8.5.4

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.