api: Remove LIMIT from queries using GIN index #2333
Merged
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
We have some queries taking a long time on the DB because for some reason the planner refuses to use the GIN index when there's a LIMIT. This is an easy fix to unblock those for now since: - on both cases the probability of having a lot of results is low - on both cases we also want to process every item that wouldn't be on the first "page" anyway
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
leszko
approved these changes
Apr 10, 2025
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.
We have some queries taking a long time on the DB because for some reason the planner refuses to use the GIN index when there's a LIMIT. This is an easy fix to unblock those for now since: