Upgrade pg_graphql to v0.1.3 #171
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
dragarcia
approved these changes
Mar 28, 2022
hf
pushed a commit
that referenced
this pull request
Jan 23, 2023
damonrand
pushed a commit
to cepro/postgres
that referenced
this pull request
Jun 15, 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.
What kind of change does this PR introduce?
Upgrades pg_graphql to version 0.1.3
Changes:
Users must manually call
graphql.rebuild_schema()after SQL DDL operations to rebuild the GraphQL schema cache. This change is in response to a performance issue for midsized to large migrationsResolves issues:
supabase/pg_graphql#127
supabase/pg_graphql#126