feature: testing the creation of auth_trgm to give auth own pg_trgm #1931
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
samrose
force-pushed
the
feat/auth-pg-trgm
branch
from
d78a1f0 to
cd3ae09
Compare
Allows supabase_auth_admin to `create extension auth_trgm`
samrose
force-pushed
the
feat/auth-pg-trgm
branch
from
e9eaf59 to
6571d30
Compare
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.
The goal:
Allow access to pg_trgm extension for auth service while not intruding on customer/user usage of pg_trgm
This pr will copy and use some files from pg_trgm to make a version that is specific for auth service to turn on and use.
By packaging this way will be kept in sync with postgres and default pg_trgm
we also limit to auth schema and make not relocatable.