-
Notifications
You must be signed in to change notification settings - Fork 4
VER-304: Optimize get_snippets filters and searching to fix timeout issues #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c74cc4c
Optimize get_snippets filters to fix timeout issues
rajivsinclair 34a19c3
Optimize get_filtering_options and get_trending_topics functions
rajivsinclair 8aa07ac
Optimize get_recording_filter_options and add missing FK indexes
rajivsinclair 05ecffa
Remove 17MB of unused indexes and optimize embedding lookup
rajivsinclair 44cb67a
Restore sorting indexes that are used by get_snippets ORDER BY
rajivsinclair c875082
Optimize state and source filters in get_snippets
rajivsinclair b402c2a
Add dislike_count tracking to snippet like trigger
quancao-ea 51463ce
Optimize database by removing unused function and adding FK indexes
quancao-ea 08a45e7
Merge get_snippets into single CTE chain and fix dislike_count
quancao-ea 66dfd6c
Update migration files
quancao-ea File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 124
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 122
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 3844
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 181
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 1477
🏁 Script executed:
cat -n supabase/migrations/20260129_optimize_filter_functions.sql | head -50Repository: PublicDataWorks/verdad
Length of output: 1933
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 550
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 423
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 48
🏁 Script executed:
Repository: PublicDataWorks/verdad
Length of output: 3050
Schema‑qualify
filter_options_cachetopublic.filter_options_cachein this SECURITY DEFINER function.The function inconsistently qualifies schema names: it explicitly uses
public.labelsandpublic.audio_fileselsewhere but leavesfilter_options_cacheunqualified on lines 67, 77, and 87. In SECURITY DEFINER functions, unqualified object names can be hijacked through search_path manipulation (includingpg_temp). Qualify the view consistently to prevent that risk.Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents