Improve indexers indexes #1068
Merged
Improve indexers indexes #1068
+194
−346
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
clostao
previously approved these changes
Jan 20, 2025
DaMandal0rian
previously approved these changes
Jan 20, 2025
Base automatically changed from
feat/optimize-consensus-indexer-logic
to
main
January 20, 2025 14:06
marc-aurele-besner
dismissed stale reviews from DaMandal0rian and clostao
The base branch was changed.
✅ Deploy Preview for dev-astral canceled.
|
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.
Improve indexers indexes
Since we don't use subquery graphql engine, we don't make much use of all the gist(*, _block_range) indexes.
Even if removed from the init-db, they get recreated everytime the indexer start if they are defined in the schema, so I removed them from the schema, and added indexes that are relevant to our most use queries.