[Pg]: pin search_path to public during migrate#6024
Open
Otto-Deviant1904 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.
Fixes #5889
When
migrations.schemamatches the Postgres DB username,CREATE SCHEMAmakes the
$usersearch_path entry resolve. UnqualifiedCREATE TABLEstatements in migration SQL then land on that schema instead of
public,while snapshots still record
public.Set
search_pathtopublicbefore applying user migration statements(
SET LOCALinside transactions; plainSETfor neon-http / pg-proxy).Added a node-postgres regression that uses
migrationsSchema = current_user.AI disclosure: assisted with investigation and the patch. I reviewed the
change and verified the approach against the issue's root-cause writeup.
Made with Cursor