From 8308d6716cf9ee3e71a7643b705d72a022eefbf2 Mon Sep 17 00:00:00 2001
From: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date: Fri, 13 Dec 2024 14:43:30 +0800
Subject: [PATCH] planner: update the fix-control doc (#19520) (#19678)

---
 optimizer-fix-controls.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/optimizer-fix-controls.md b/optimizer-fix-controls.md
index a86e6a5299e27..d6007621fbb13 100644
--- a/optimizer-fix-controls.md
+++ b/optimizer-fix-controls.md
@@ -58,3 +58,9 @@ SET SESSION tidb_opt_fix_control = '44262:ON,44389:ON';
 - In some scenarios, when the `Probe` side of an `IndexJoin` operator contains a `Selection` operator, TiDB severely overestimates the row count of `IndexScan`. This might cause suboptimal query plans to be selected instead of `IndexJoin`.
 - To mitigate this issue, TiDB has introduced an improvement. However, due to potential query plan fallback risks, this improvement is disabled by default.
 - This variable controls whether to enable the preceding improvement.
+
+### [`46177`](https://github.com/pingcap/tidb/issues/46177) <span class="version-mark">New in v6.5.6 and v7.1.3</span>
+
+- Default value: `ON`
+- Possible values: `ON`, `OFF`
+- This variable controls whether the optimizer explores enforced plans during query optimization after finding an unenforced plan.