PG: Add per index blocks hit and blocks read #20767
Merged
+10
−71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
pg_statio_user_indexes
provides per index block usage. It is usingpg_stat_get_blocks_fetched
andpg_stat_get_blocks_hit
behind the hood. We can emit those metrics directly from our IDX_METRICS query.The metric name
postgresql.index.blocks_read
was used aspostgresql.index_blocks_read
already exists for the per table block usage.Motivation
This would provide a better granularity of the index block usage.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged