Still an issue: ERROR: must be owner of extension vector

Product Support

AI-generated summary

The discussion revolves around resolving the ERROR: must be owner of extension vector issue. Despite prior reports of a fix, ja3 still encounters the problem when running launcher rebuild app with a single container on a Linux VM and an Azure Postgresql Flexible Server database.

Falco suggests the error occurs when the configured database user isn’t the owner of the extension. To resolve this, he recommends logging into the database with the owner user and running ALTER EXTENSION vector UPDATE TO '0.7.0';.

ja3 confirms this solution works, but notes that Azure doesn’t allow specifying the version. Instead, running ALTER EXTENSION vector UPDATE updates to the latest available version. ja3 provides instructions on how to check the current installed version and update it.

1

There has been a few threads about this issue, which includes responses from the contributors that the issue has been fixed in docker_manager.

But I still have this issue running launcher rebuild app. I use a single container (on a linux VM), and the database is hosted on Azure Postgresql Flexible Server.

image
image2834×456 60.2 KB

Further down…

The image displays a stack trace with error messages related to PostgreSQL privileges and Ruby/Gem dependencies. (Captioned by AI)
The image displays a stack trace with error messages related to PostgreSQL privileges and Ruby/Gem dependencies. (Captioned by AI)2848×330 46.6 KB

Final summary

image
image2864×410 41.6 KB

Has anyone managed to figure out a solution with this setup (Azure Postgresql) ?

PS: I’m continuing to run discourse with the AI plugin disabled for now.

2

If the user you have configured for this database isn’t the owner of the extension, it will fail with the message shared above: ERROR: must be the owner of the extension vector.

To workaround this issue, log to the database directly with the user who is the owner and run ALTER EXTENSION vector UPDATE TO '0.7.0';.

3

Thanks @Falco that solved the issue for me!

Since Azure doesn’t allow specifying the version I ran ALTER EXTENSION vector UPDATE to update to the latest available version. The extension installs are specific to the database, so need to connect to the discourse database (not the default postgres db) to run the update statement.

Here’s how to check the current installed version and to update.

The image shows a SQL query executed in a PostgreSQL environment, updating the version of the 'vector' extension, and the updated version is displayed after the query is executed. (Captioned by AI)
The image shows a SQL query executed in a PostgreSQL environment, updating the version of the 'vector' extension, and the updated version is displayed after the query is executed. (Captioned by AI)2506×694 34.6 KB

SELECT name, default_version, installed_version FROM pg_available_extensions WHERE name = 'vector';