Issue #37 - Create indexes on Postgres - #424
Open
Uliana-Karavatskaya wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue number: resolves #37
Checklist
What is the current behavior?
Queries filtering bookmarks and tags rely only on primary key indexes. Frequently used search patterns (
user_id,user_id + url,user_id + tag_title,tag_id) are not covered by indexes, which can lead to sequential scans and slower query performance on larger datasets.Added database indexes to optimize frequently used lookup queries:
bookmark(user_id, url)bookmark_tag(tag_id)tag(user_id, tag_title)Added a Flyway migration to apply these indexes.
Does this introduce a breaking change?
Other information
The indexes were verified after migration. On the current development database, PostgreSQL may still choose sequential scans because the tables contain very little data.
EXPLAINconfirms that the new indexes are available and can be used by the query planner.