Skip to content

Commit

Permalink
planner: update the fix-control doc (pingcap#19520)
Browse files Browse the repository at this point in the history
  • Loading branch information
qw4990 authored and Oreoxmt committed Dec 13, 2024
1 parent ff81524 commit 48308c0
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions optimizer-fix-controls.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,16 @@ 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.

### [`45132`](https://github.com/pingcap/tidb/issues/45132) <span class="version-mark">New in v7.4.0</span>

- Default value: `1000`
- Possible values: `[0, 2147483647]`
- This variable sets the threshold for the optimizer's heuristic strategy to select access paths. If the estimated rows for an access path (such as `Index_A`) is much smaller than that of other access paths (default `1000` times), the optimizer skips the cost comparison and directly selects `Index_A`.
- `0` means to disable this heuristic strategy.

### [`46177`](https://github.com/pingcap/tidb/issues/46177) <span class="version-mark">New in v6.5.6</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.

0 comments on commit 48308c0

Please sign in to comment.