Enabling pgvector extension on Managed Postgres cluster

[devonluongo]

I need the pgvector extension enabled on my Managed Postgres
cluster.

Cluster ID: nlkxjo5q2mloy93v
Cluster name: ai-agent-mvp-db
Database: fly-db
Extension needed: vector (pgvector)

The fly-user (schema_admin) doesn’t have superuser privileges
to run CREATE EXTENSION. Please enable it or grant the
necessary permissions.

[halfer]

Related:

Is it possible to deploy Fly.io’s managed Postgres with pgvector available for installation (via CREATE EXTENSION) with zero end-user intervention?

We’re building a hands-free installer for GoodMem on fly.io that deploys a Postgres instance automatically. Today, we deploy Postgres using a custom image (pgvector/pgvector:pg17) so that pgvector is guaranteed to be available, and our server installs the extension automatically on first startup. We’d prefer to use Fly.io’s managed Postgres offering, but only if there’s a way to ensure that pgvector is already available in the managed Postgres instance, so that CREATE EXTENSION vector; succeed…

[halfer]

Ah, this suggests you can add it yourself:

MPG extensions management is here

[image] Fly Managed Postgres now includes a built-in Extensions page in the dashboard, so you can toggle PG extensions on or off with a click. No weird commands to run—just flip the switch! You’ll be prompted to pick or create a schema to install the extension in. In most cases public or extensions are fine options, but you can achieve namespace scoping by installing extensions into their own schemas, then using functions fully-qualified: SELECT citext.citext_ne('Hello', 'World'); Right no…