On 9/30/25 6:35 AM, mrudula attili wrote:
Hello Team,
Concern:
As its a production environment, we are not really happy to give away
the usage on public schema.
Is there a way we could get the end users make use of the extension
without granting usage on public schema
In addition to what Tom Lane suggested:
https://github.com/pgvector/pgvector/blob/master/vector.control
relocatable = true
And per here:
https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-RELOCATION
"
A fully relocatable extension can be moved into another schema at any
time, even after it's been loaded into a database. This is done with the
ALTER EXTENSION SET SCHEMA command, which automatically renames all the
member objects into the new schema. Normally, this is only possible if
the extension contains no internal assumptions about what schema any of
its objects are in. Also, the extension's objects must all be in one
schema to begin with (ignoring objects that do not belong to any schema,
such as procedural languages). Mark a fully relocatable extension by
setting relocatable = true in its control file.
"
You could move the extension to a schema that the users do have usage on.
Thanks,
SA
--
Adrian Klaver
[email protected]
