-
-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use safeupdate for the database nor the postgres user (session_preload_libraries) #1308
Comments
Hi @activenode , Thanks for opening. Can you confirm your instance is running the latest version: Trying both options work for me with the Enabling it for the entire database is the second option, per user can be useful for those using the API or wanting to enforce it in to more specific use cases. |
I've created a new project on supabase.com and tried this. I can do it again. Will get back to you soon |
(I need to add: This is definitely still possible with older projects if you've tried that) |
Can you confirm this? @encima ? |
hey @activenode I just tried running both as a single transaction and 2 separate ones without issue 🤔 |
Will create a new one and make a video |
Completely fresh project on supbase.com (I try setting it first, then altering, then trying again, just to show it doesn't work no matter what I do) ne.mov |
Also tried it now on a FRESH |
My team is facing the same issue actually |
I just followed the instruction from the docs with replacing "anon" by postgres and I also get a permission denied error (ERROR: 42501) |
I am seeing the same error |
Hey folks, thanks for confirming these! What I have found in testing is this:
Can you confirm this is what you are experiencing as well? Update: it seems like the comments above are from new projects so there is not much of a pattern 🤷♀️ |
Cannot confirm. Happens for new projects as well as happened for old projects on my end. What I can confirm though is: On SOME old projects it worked. |
For me this also appeared on a freshly created project |
Thanks folks, this has been escalated to @supabase/postgres and I will get back here when we know more |
Hey all, quick update from our side: This issue is being resolved through our included utils library We will link the PR when it is out and then update the documentation to reflect the changes. Thanks for reporting this and for your patience! |
Any update on this? |
hey @imownbey update to the docs incoming tomorrow but we have a fix in place that is implemented by supautils. |
Hello all, It has been identified that modifying Apologies for the inconvenience, we really want to make sure that we minimise breaking changes and maintain a consistent experience as much as possible. |
Bug report
Basically, this worked in older projects. In newer projects, the permissions are stricter and one cannot enable this, safeguarding,
safeupdate
extension. But this is a crucial help for avoiding human failure.Describe the bug
It's all said.
To Reproduce
Try either of the provided options in the intro.
Expected behavior
safeupdate
can be enabled in the database (I don't think we necessarily needpostgres
role setting but rather one config that enables this in the database or not).Screenshots
The text was updated successfully, but these errors were encountered: