From 348f39a74309603ae7cbb8b2e761c128865441b1 Mon Sep 17 00:00:00 2001
From: joey-yez <104608045+joey-yez@users.noreply.github.com>
Date: Fri, 29 Dec 2023 17:06:30 +0800
Subject: [PATCH] Update use-tidb-to-read-tiflash.md (#15885)

---
 tiflash/use-tidb-to-read-tiflash.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tiflash/use-tidb-to-read-tiflash.md b/tiflash/use-tidb-to-read-tiflash.md
index 325f1e25d5f74..900122e430380 100644
--- a/tiflash/use-tidb-to-read-tiflash.md
+++ b/tiflash/use-tidb-to-read-tiflash.md
@@ -143,4 +143,6 @@ In the above three ways of reading TiFlash replicas, engine isolation specifies
 
 > **Note:**
 >
-> Before v4.0.3, the behavior of reading from TiFlash replica in a non-read-only SQL statement (for example, `INSERT INTO ... SELECT`, `SELECT ... FOR UPDATE`, `UPDATE ...`, `DELETE ...`) is undefined. In v4.0.3 and later versions, internally TiDB ignores the TiFlash replica for a non-read-only SQL statement to guarantee the data correctness. That is, for [smart selection](#smart-selection), TiDB automatically selects the non-TiFlash replica; for [engine isolation](#engine-isolation) that specifies TiFlash replica **only**, TiDB reports an error; and for [manual hint](#manual-hint), TiDB ignores the hint.
+> - Before v4.0.3, the behavior of reading from TiFlash replica in a non-read-only SQL statement (for example, `INSERT INTO ... SELECT`, `SELECT ... FOR UPDATE`, `UPDATE ...`, `DELETE ...`) is undefined.
+> - For versions from v4.0.3 to v6.2.0, internally TiDB ignores the TiFlash replica for a non-read-only SQL statement to guarantee the data correctness. That is, for [smart selection](#smart-selection), TiDB automatically selects the non-TiFlash replica; for [engine isolation](#engine-isolation) that specifies TiFlash replica **only**, TiDB reports an error; and for [manual hint](#manual-hint), TiDB ignores the hint.
+> - For versions from v6.3.0 to v6.5.x, if the TiFlash replica is enabled, you can use the [`tidb_enable_tiflash_read_for_write_stmt`](/system-variables.md#tidb_enable_tiflash_read_for_write_stmt-new-in-v630) variable to control whether TiDB uses the TiFlash replica for a non-read-only SQL statement.