| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This change is part of the following stack: Change managed by git-spice. |
Sorry, something went wrong.
|
Skipping CI for Draft Pull Request. |
Sorry, something went wrong.
🚀 Build Images ReadyImages are ready for commit 936152f. To use with deploy scripts: export MAIN_IMAGE_TAG=4.11.x-1045-g936152f929 |
Sorry, something went wrong.
Query pg_stat_user_indexes joined with pg_index to capture index validity, type, size, and scan count. Scoped to current user's indexes to avoid leaking metadata from external database management schemas. Output written to central-db-pg-index-stats.json. Partially generated by AI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
/test create-custom-snapshot |
Sorry, something went wrong.
|
/retest |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Query pg_stat_user_indexes joined with pg_index to capture index
validity, type, size, and scan count. Scoped to current user's
indexes to avoid leaking metadata from external database management
schemas. Output written to central-db-pg-index-stats.json.
Partially generated by AI.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Deployed cluster. Ran diagnostic bundle with all valid indexes. Ran diagnostic bundle with an invalid index present.
When all indexes are valid, they are all marked as valid in the diagnostic bundle. On the invalid test they are not. See
{ "TableName": "alerts", "IndexName": "alerts_state", "IndexType": "btree", "IndexSizeBytes": 16384, "IsValid": false, "IsReady": true, "IndexScans": 0 },