You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a migration with
CREATE EXTENSION "vector";
ALTER EXTENSION "vector"SET SCHEMA extensions;
The following error is returned
Error: ERROR: must be owner of extension vector (SQLSTATE 42501)
At statement 2: ALTER EXTENSION "vector" SET SCHEMA extensions
This is due to the extension having the id of supabase_admin as its user listed in pg_extension.extowner. However, via the CLI, it is not possible to change extowner 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
OS: macOS
Version of supabase-cli: 1.50.4
The text was updated successfully, but these errors were encountered:
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: