This repository has been archived by the owner on Dec 17, 2024. It is now read-only.
[+] add metric and dashboard for bloated indexes and tables #518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Grafana screenshots |
pashagolub
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since there is no panel in TablesTop that shows which table is bloated, it was added based on the existing table_bloat_approx_stattuple metric.
Following the same line and based on the experience of some cases where I have seen indexes bloats, a metric based on the pgstattuple extension with the help pgstatindex (leaf_fragmentation) function is proposed.
All this was tested in PostgreSQL 12.