Repository navigation
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
TiDB #70833 收敛为仅新增 PREWRITE_BACKOFF_TYPES 与 COMMIT_BACKOFF_TYPES 两列;撤销 COP_BACKOFF_TYPES。相应移除该列的表结构输出、列说明与 按 cop 类型筛选的示例,改为按事务 backoff 类型筛选的示例,并说明 coprocessor 阶段类型仍可通过 Backoff_Detail 查看。
|
对齐 pingcap/tidb#70833 的 L1 范围:仅新增 |
Signed-off-by: jiong-nba <jiongnba@gmail.com>
Signed-off-by: jiong-nba <jiongnba@gmail.com>
What is changed, added, or deleted? (Required)
Document
Prewrite_Backoff_typesandCommit_Backoff_typesfrom TiDB #70833 in the system-table reference and slow-query examples. The existingBackoff_typescolumn reads only the original log field, preserving its value (including empty strings and[]); it returns''when that field is absent. The raw slow log format is unchanged, and direct-file tools need separate support for phase fields.Describe phase coverage, missing values, bracketed list format and duplicates. Coprocessor types remain in
Backoff_Detail. New columns are appended afterQuery;SELECT *changes shape, and new-column cluster queries require all queried nodes to support the schema during rolling upgrades.Draft dependency: merge after pingcap/tidb#70833. The first released version and release-branch backports remain unconfirmed; master only. English and Chinese use the same rules, column order and SQL examples.
Validation: targeted Markdown lint and internal links passed. English and Chinese changes were checked for matching field behavior, column order, and SQL examples. A real local PD/TiKV v8.5.7 cluster with TiDB 067c50bd46 (before this feature) and 97a61122cc verified both reader directions, explicit old/new projections and SELECT *. SQL/Go model/CSV and Python JSON/CSV/SQLite TEXT preserved 1452/1332-character phase values. Dashboard phase integration is tracked in pingcap/tidb-dashboard#1950; representative API and ui-v2 detail fixtures were verified. Other historical schema combinations, deployed raw-file pipelines and production throughput remain unverified.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?