From 7be9554af0907e9baf3eea14c184e0af83b07684 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Wed, 13 Mar 2024 18:36:41 +0800 Subject: [PATCH] *: add notice on flashback cluster usage (#16738) (#16759) --- sql-statements/sql-statement-flashback-cluster.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sql-statements/sql-statement-flashback-cluster.md b/sql-statements/sql-statement-flashback-cluster.md index 83a362b3b31af..ae37dc69b7faf 100644 --- a/sql-statements/sql-statement-flashback-cluster.md +++ b/sql-statements/sql-statement-flashback-cluster.md @@ -14,6 +14,10 @@ Starting from v6.5.6, v7.1.3, and v7.5.1, TiDB introduces the `FLASHBACK CLUSTER > > The `FLASHBACK CLUSTER TO [TIMESTAMP|TSO]` syntax is not applicable to [TiDB Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless) clusters. To avoid unexpected results, do not execute this statement on TiDB Serverless clusters. +> **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. + > **Warning:**