Skip to content

Commit f8a5841

Browse files
craig[bot]maryliag
andcommitted
Merge #118964
118964: doc: update index_recommendations.md r=maryliag a=maryliag The indentation of footnote was incorrect, making it not load. This commit just fix it. Part Of CRDB-35839 Release note: None Co-authored-by: Marylia Gutierrez <[email protected]>
2 parents 5ad907e + 061b81e commit f8a5841

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

docs/tech-notes/observability/index_recommendations.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -85,13 +85,13 @@ All options above will display a button to create/alter/drop the index directly
8585
from the Console UI.
8686

8787
[^1]: The cost of generating index recommendations is highly variable. Index recommendations are generated by:
88-
1. Analyzing the query to find "hypothetical indexes" that may improve the performance of the query.
89-
2. Running the query optimizer as if the hypothetical indexes actually exist.
90-
3. Any hypothetical index in the final query plan becomes an index recommendation.
91-
92-
Step 1 is not picky. Its goal is to cover all possible indexes that might help.
93-
In general, the number of hypothetical indexes grows with the number of filtered columns
94-
in the query.
95-
Step 2 can be fast for simple queries (<1ms), but the cost of optimization grows with
96-
the number of joins, filters, and columns (>1s).
97-
If Step 1 adds many hypothetical indexes, Step 2 will take longer because there are more query plans to explore.
88+
1. Analyzing the query to find "hypothetical indexes" that may improve the performance of the query.
89+
2. Running the query optimizer as if the hypothetical indexes actually exist.
90+
3. Any hypothetical index in the final query plan becomes an index recommendation.
91+
92+
Step 1 is not picky. Its goal is to cover all possible indexes that might help.
93+
In general, the number of hypothetical indexes grows with the number of filtered columns
94+
in the query.
95+
Step 2 can be fast for simple queries (<1ms), but the cost of optimization grows with
96+
the number of joins, filters, and columns (>1s).
97+
If Step 1 adds many hypothetical indexes, Step 2 will take longer because there are more query plans to explore.

0 commit comments

Comments
 (0)