-
-
Notifications
You must be signed in to change notification settings - Fork 128
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 ALTER EXTENSION
due to owner conflicts
#725
Labels
bug
Something isn't working
Comments
Transferred from CLI repo because it also affects the hosted platform. |
any updates on this? |
Any updates? |
If you use prisma, try this.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Describe the bug
When trying to alter an an extension in a migration after installation in a previous migration, the operation fails due to ownership conflicts.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
This is due to the extension having the id of
supabase_admin
as its user listed inpg_extension.extowner
. However, via the CLI, it is not possible to changeextowner
to the id of postgres, and there seems to be no programmatic way of changing the owner of an extension.In some cases, the extension can be dropped and reinstalled. But if you already use a
vector
data type in a table, the operation will fail.Expected behavior
alter extension [ext] set schema [schema]
should work via the CLI as long as the extension is relocatable.System information
The text was updated successfully, but these errors were encountered: