pgvector on new Postgres, plus Postgres 18 images
The Postgres template ships the vector extension, Postgres 18 images boot on the usual volume path, and PostGIS and TimescaleDB get full database tooling.
New Postgres databases created from the template use the official Postgres 16 image with pgvector included. Run CREATE EXTENSION vector; to store embeddings, and apps that need it, such as Chatwoot 4, migrate without extra steps. Existing databases keep their image.
Postgres 18 on the usual mount
Postgres 18 images refuse a volume mounted at /var/lib/postgresql/data unless PGDATA is set. When you deploy a Postgres 18 or newer image with its volume at that path and no PGDATA of your own, Unbroker sets it for you. Versions 17 and older are never changed.
PostGIS, TimescaleDB and pgvector images
Services that run postgis/postgis, timescale/timescaledb or pgvector/pgvector are recognized as Postgres. They get the database tunnel, the data browser, pg_dump backups and database resource defaults. A volume created before this keeps the owner it already had, so redeploying it is safe.