[schemas] Text search trigram index for ILIKE fallback#206
Merged
justfinethanku merged 5 commits intoJun 1, 2026
Merged
Conversation
Collaborator
Author
|
Mergeable, no conflicts against |
justfinethanku
approved these changes
Jun 1, 2026
justfinethanku
left a comment
Collaborator
There was a problem hiding this comment.
Maintainer review: Alan's triage says this is mergeable with no blockers and ready for queue. I updated the branch against main, added the repo community badge/creator credit convention, ran markdownlint locally, and GitHub label/lint checks are passing.
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
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.
What this adds
schemas/text-search-trgm/— installs `pg_trgm` + creates a trigram GIN index on `public.thoughts.content` so `search_thoughts_text` ILIKE fallback queries drop from ~8s to ~150ms.Perf impact
Prerequisites
Install-time
`ANALYZE public.thoughts;` is an explicit post-migration step (Step 4) — planner needs refreshed stats to pick the index immediately.
Review history
Iteratively refined across 3 rounds. Final Codex + Claude reviews clean.
See `schemas/text-search-trgm/README.md`.