Drop 9 unused database indexes to reclaim 3.36 GiB of storage #2
Conversation
This file contains hidden or 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
Addresses Postgres.AI issue H002: Unused Indexes consuming 11% of database size. All identified indexes have zero scans recorded over a 31-day observation period. Changes: - Removed 4 unused indexes from Product table (2.26 GiB) - Removed 1 unused index from Customer table (206 MiB) - Removed 3 unused indexes from Order table (397 MiB) - Removed 1 unused index from OrderItem table (132 MiB) Migration uses DROP INDEX CONCURRENTLY to avoid production impact. Issue: https://console.postgres.ai/goodvibes-ai/issues/019a5a58-582f-7819-9377-b40d207aa220
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses Postgres.AI issue H002: Unused Indexes consuming 11% of database size. All identified indexes have zero scans recorded over a 31-day observation period.
Changes:
Migration uses DROP INDEX CONCURRENTLY to avoid production impact.
Issue: https://console.postgres.ai/goodvibes-ai/issues/019a5a58-582f-7819-9377-b40d207aa220