Skip to content

Commit 25b78ad

Browse files
committed
fix ref in doc
1 parent d69607e commit 25b78ad

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

doc/user/content/sql/explain-analyze.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -207,9 +207,8 @@ CREATE INDEX wins_by_item ON winning_bids (item);
207207
```
208208

209209
Re-running the `TopK`-hints query will show only `null` hints; there are no
210-
hints because our `TopK` is now appropriately sized. But if we re-run our [query
211-
for attributing memory usage](#attributing-memory-usage), we can see that our
212-
`TopK` operator uses a third of the 100MB of memory it was using before:
210+
hints because our `TopK` is now appropriately sized. But if we re-run `EXPLAIN ANALYZE MEMORY FOR INDEX wins_by_item`, we can see that our
211+
`TopK` operator uses a third of the ~100MB of memory it was using before:
213212

214213
| operator | total_memory | total_records |
215214
| -------------------------------- | ------------ | ------------- |

0 commit comments

Comments
 (0)