Modify safeupdate usage to fit with extension changes #27892
Closed
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Skipped Deployments
|
|
No changes detected in Branching Preview Branches by Supabase. |
soedirgo
reviewed
Jul 10, 2024
soedirgo
reviewed
Jul 10, 2024
soedirgo
approved these changes
Jul 10, 2024
charislam
approved these changes
Jul 10, 2024
encima
force-pushed
the
docs/pg-safeupdate-amendments
branch
from
d911de1 to
76f4d83
Compare
encima
force-pushed
the
docs/pg-safeupdate-amendments
branch
from
76f4d83 to
ea53848
Compare
charislam
approved these changes
Jul 12, 2024
Co-authored-by: Charis <[email protected]>
|
the page |
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.
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
docs update
What is the current behavior?
Current behaviour is inconsistent across project versions and can result in permissions errors
What is the new behavior?
New behaviour loads
safeupdateby default intoshared_preload_libraries(for all versions after 15.1.173) and can then be enabled on a per-role basis.Closes supabase/postgres#1308