• Use index order to avoid extra sorting operations for SQL queries like WHERE idx �→ _col_1 IS NULL ORDER BY idx_col_2 #54188 @ari-e • Display analyzed indexes in the mysql.analyze_jobs system table #53777 @Leavrth • Make incremental backups compatible with point-in-time recovery (PITR) #54474 @3pointer • Support backing up and restoring the mysql.column_stats_usage table #53567 @hi-rustin 2.2.5 #54870 @qw4990 • Fix the issue that the error runtime error: invalid memory address or nil �→ pointer dereference might occur when executing SQL statements with tidb_enable_inl_join_inner_multi_pattern enabled

restarts, cluster scaling-out, and network jitter when backing up large numbers of tables #52534 @3pointer • Implement fine-grained checks of TiCDC changefeed during data restore. If the changefeed CheckpointTS • Add a tikv_log_backup_pending_initial_scan monitoring metric in the Grafana dashboard #16656 @3pointer • Optimize the output format of PITR logs and add a RestoreTS field in the logs #53645 @dveeden conditions in queries might cause the planner module to report an invalid memory address or nil pointer dereference error #53582 #53580 #53594 #53603 @YangKeao • Fix the issue that executing CREATE OR REPLACE

· · · · · · · · · · · · · · · · · · · · · 1207 11 7.7.17 How does TiCDC Open Protocol represent null? · · · · · · · · · · · · · · · · · · 1207 7.7.18 How can I tell if a Row Changed Event of TiCDC Open added, the type is changed from boolean to enu- mera- tion, the default value is changed from OFF to null, and the op- tional values TABLE and GLOBAL are added. In ad- dition, it now sup- ports cluster- level estimates the number of rows as 1 when accessing a unique index with the query condition column IS NULL #56116 @hawkingrei • Fix the issue that the optimizer does not use the best multi-column statistics

added, the type is changed from boolean to enu- mera- tion, the default value is changed from OFF to null, and the op- tional values TABLE and GLOBAL are added. In ad- dition, it now sup- ports cluster- level estimates the number of rows as 1 when accessing a unique index with the query condition column IS NULL #56116 @hawkingrei • Fix the issue that the optimizer does not use the best multi-column statistics #49692 @solotzg • Fix the issue that the SUB_PART value in the INFORMATION_SCHEMA.STATISTICS table is NULL #55812 @Defined2014 • Fix the issue that an error occurs when a DML statement contains nested gener-

earlier versions, when processing a transaction containing UPDATE changes, if the primary key or non-null unique index value is modified in an UPDATE event, TiCDC splits this event into DELETE and INSERT Authen- tication requests with user- names not in this list will be rejected. The default value is null. TiCDC security �→ . �→ client �→ - �→ user �→ - �→ required �→ Newly added Controls whether to use CPS by type metric displays incorrect values #52605 @nolouch 56 • Fix the issue that the nil pointer error occurs when you query INFORMATION_ �→ SCHEMA.TIKV_REGION_STATUS #52013 @JmPotato • Fix the

@guo-shaoge • Tools – Backup & Restore (BR) * 优化备份功能，提升在大量表备份过程中遇到节点重启、扩容或网络抖动时的备份性能和稳 定性 #52534 @3pointer * 优化恢复过程中对 TiCDC Changefeed 的细粒度检查，如果 Changefeed 的CheckpointTS 晚于数据的备 份时间，则不会影响恢复操作，从而减少不必要的等待时间，提升用户体验 支持对日志备份过程中生成的临时文件进行加密 #15083 @YuJuncen * 在 Grafana 面板中新增 tikv_log_backup_pending_initial_scan 监控指标 #16656 @3pointer * 优化 PITR 日志的输出格式，并在日志中新增 RestoreTS 字段 #53645 @dveeden – TiCDC * 支 持 当 下 游 为 消 息 队 列 (Message (stats_meta) 的问题 #53652 @hawkingrei – 修复查询中的某些过滤条件可能导致 planner 模块发生 invalid memory address or nil pointer �→ dereference 报错的问题 #53582 #53580 #53594 #53603 @YangKeao – 修复并发执行 CREATE OR REPLACE VIEW 可能报错 table doesn't

7.8.16 TiCDC 把数据同步到 Kafka 时，如何确定一条消息中包含的数据变更发生在哪个时间点？ · · · · 954 7.8.17 TiCDC Open protocol 如何标示 null 值？ · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 954 10 7.8 #55981 @winoros – 修复统计信息初始化时，使用非二进制排序规则的字符串类型列的统计信息可能无法正常加载的 问题 #55684 @winoros – 修复当查询条件为 column IS NULL 访问唯一索引时，优化器将行数错误地估算为 1 的问题 #56116 @hawkingrei – 修复当查询包含形如 (... AND ...)OR (... AND ...)... 的过滤条件时，优化器没有使用最优的 前台限流 Y Y Y Y Y Y Y E N N N N 后台限流 E E E E E E E N N N N N 5从TiDB v7.0.0 开始新增的参数 FIELDS DEFINED NULL BY 以及新增支持从 S3 和 GCS 导入数据，均为实验特性。从TiDB v7.6.0 开始 LOAD DATA 的事务行为与 MySQL 的事务行为一致，包括事务内的 LOAD DATA

#55981 @winoros – 修复统计信息初始化时，使用非二进制排序规则的字符串类型列的统计信息可能无法正常加载的 问题 #55684 @winoros – 修复当查询条件为 column IS NULL 访问唯一索引时，优化器将行数错误地估算为 1 的问题 #56116 @hawkingrei – 修复当查询包含形如 (... AND ...)OR (... AND ...)... 的过滤条件时，优化器没有使用最优的 Y Y Y Y Y Y Y Y Kubernetes operator Y Y Y Y Y Y Y Y Y Y Y Y 5从TiDB v7.0.0 开始新增的参数 FIELDS DEFINED NULL BY 以及新增支持从 S3 和 GCS 导入数据，均为实验特性。从TiDB v7.6.0 开始 LOAD DATA 的事务行为与 MySQL 的事务行为一致，包括事务内的 LOAD DATA playerRepository.save(player); 更多信息参考插入数据和更新数据。 查询数据 PlayerBean player = playerRepository.findById(id).orElse(null); 更多信息参考查询数据。 删除数据 playerRepository.deleteById(id); 更多信息参考删除数据。 4.3.1.4.4 下一步 • 关于本文使用到的第三方库及框架，可以参考各自官方文档：

Performance • BR improves snapshot restore speed by up to 10 times (experimental) #33937 #49886 @3pointer As a TiDB cluster scales up, it becomes increasingly crucial to quickly restore the clus- ter from Refactor the BR exception handling mechanism to increase tolerance for un- known errors #47656 @3pointer • TiCDC • Improve the performance of TiCDC replicating data to object storage by increasing parallelism TiDB • Fix the issue that TiDB panics and reports an error invalid memory address �→ or nil pointer dereference #42739 @CbcWestwolf • Fix the TiDB node panic issue that occurs when DDL jobID is restored

Authen- tication requests with user- names not in this list will be rejected. The default value is null. TiCDC security �→ . �→ client �→ - �→ user �→ - �→ required �→ Newly added Controls whether to use the CPS by type metric displays incorrect values #52605 @nolouch • Fix the issue that the nil pointer error occurs when you query INFORMATION_ �→ SCHEMA.TIKV_REGION_STATUS #52013 @JmPotato • Fix the removing a log backup task after it is paused does not immediately restore the GC safepoint #52082 @3pointer • Fix a rare issue that special event timing might cause the data loss in log backup #16739 @YuJuncen