8 months ago
Hi Railway team,
I'm currently working on a project using a pgvector service and I had a quick question about extension scope:
Is it possible to have two separate schemas, both containing the vector extension, within the same pgvector service?
From what I've observed so far, it seems that the extension can only be installed once per database, and its objects (like the vector type) are bound to a single schema. When I try to create the extension in a second schema, I receive a notice saying it's already installed and the action is skipped.
Is this a PostgreSQL limitation, a pgvector-specific constraint, or something that Railway imposes at the service level?
Thanks in advance for the clarification.
Best regards
3 Replies
8 months ago
Railway does not impose any kind of limitation like you mentioned at service level.
But then how can I set the extension to a new schema without removing it from the current one?
Postgres seems to allow it in only one schema at a time. Any workaround?