We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent d69607e commit 25b78adCopy full SHA for 25b78ad
doc/user/content/sql/explain-analyze.md
@@ -207,9 +207,8 @@ CREATE INDEX wins_by_item ON winning_bids (item);
207
```
208
209
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:
+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
+`TopK` operator uses a third of the ~100MB of memory it was using before:
213
214
| operator | total_memory | total_records |
215
| -------------------------------- | ------------ | ------------- |
0 commit comments