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.

Sign up for GitHub

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 #19347

Merged
merged 5 commits into from
Dec 16, 2024
Merged

flashback: add limitation with stale read/snapshot #19347

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
468fd6c
Add temp.md
qiancai Nov 6, 2024
bc283f0
Delete temp.md
qiancai Nov 6, 2024
dac7a23
Update sql-statement-flashback-cluster.md
qiancai Nov 6, 2024
a4ce348
Update sql-statements/sql-statement-flashback-cluster.md
qiancai Nov 7, 2024
383dc28
Update sql-statements/sql-statement-flashback-cluster.md
qiancai Dec 16, 2024
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
3 changes: 2 additions & 1 deletion sql-statements/sql-statement-flashback-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,8 @@ Starting from v6.5.6, v7.1.3, v7.5.1, and v7.6.0, TiDB introduces the `FLASHBACK

> **Warning:**
>
> When specifying a recovery point in time, make sure to check the validity of your target timestamp or TSO and avoid specifying a future time that exceeds the maximum TSO currently allocated by PD (see `Current TSO` on the Grafana PD panel). Otherwise, concurrent processing linear consistency and transaction isolation levels might be violated, leading to serious data correctness issues.
> - When specifying a recovery point in time, make sure to check the validity of your target timestamp or TSO and avoid specifying a future time that exceeds the maximum TSO currently allocated by PD (see `Current TSO` on the Grafana PD panel). Otherwise, concurrent processing linear consistency and transaction isolation levels might be violated, leading to serious data correctness issues.
> - During `FLASHBACK CLUSTER` execution, the data cleanup process does not guarantee transaction consistency. After `FLASHBACK CLUSTER` completes, if you intend to use any historical version reading features in TiDB (such as [Stale Read](/stale-read.md) or [`tidb_snapshot`](/read-historical-data.md)), make sure that the specified historical timestamp falls outside the `FLASHBACK CLUSTER` execution period. Reading a historical version that includes data not fully reverted by FLASHBACK might violate concurrent processing linear consistency and transaction isolation levels, leading to serious data accuracy issues.
qiancai marked this conversation as resolved.
Show resolved Hide resolved

<CustomContent platform="tidb">

Expand Down
Loading