Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flashback: add limitation with stale read/snapshot #18903

Merged
merged 5 commits into from
Dec 16, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions sql-statements/sql-statement-flashback-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ TiDB v6.5.6、v7.1.3、v7.5.1、v7.6.0 开始引入了 `FLASHBACK CLUSTER TO TSO
> **警告:**
>
> 在指定恢复时间点时,请务必检查 TIMESTAMP 或 TSO 的有效性,避免指定可能超过 PD 当前分配的最大 TSO(参考 Grafana PD 面板上 `Current TSO`)的未来时间。否则,可能破坏并发处理线性一致性以及事务隔离级别,导致严重的数据正确性的问题。
> 在执行 FLASHBACK 时,数据不会通过事务进行清理。请确保在 FLASHBACK 完成后,未来使用 TiDB 的任何历史版本读取功能(如 Stale Read 或 Set Snapshot)时,选择的时间点不要落在 FLASHBACK 运行的时间范围内。如果读取的历史版本包含未完成的 FLASHBACK 数据,可能破坏并发处理线性一致性以及事务隔离级别,导致严重的数据正确性的问题。
3pointer marked this conversation as resolved.
Show resolved Hide resolved

> **警告:**
>
Expand Down