Esta página se tradujo automáticamente. Leer el original en inglés.

Component

core/datastore/pgvector

A vector database on the PostgreSQL engine: PostgreSQL with the pgvector extension, which adds a vector column type, distance operators and approximate nearest-neighbour indexes, so embeddings are stored beside ordinary rows and queried by similarity in SQL. The server runs the pgvector project's own image, which carries the extension, and the database the component creates has it enabled. Wire here when an application retrieves by similarity and keeps its vectors in PostgreSQL; core/datastore/postgres is the general-purpose relational store, and core/datastore/qdrant, core/datastore/weaviate and core/datastore/chroma are vector stores with APIs of their own. It presents the standard PostgreSQL wire contract (POSTGRES_USER / POSTGRES_PASSWORD / POSTGRES_DB) and exports its host, port, user, database and protocol, and an endpoint joining them into a connection URI that carries no password, so a socket selecting vector stores admits it and a consumer reaches it with a PostgreSQL client. Realized two ways, both self-hosted and both fetching nothing: reach for the Helm Recipe on Kubernetes, which synthesizes a StatefulSet with a persistent volume, and for the Compose Recipe for local development. Its Recipes are verified by their rendered output, not by a started server storing and querying vectors. RDS for PostgreSQL offers pgvector on PostgreSQL 12-19, but no setting of the database instance enables it in a database, only a CREATE EXTENSION statement, so no RDS Recipe realizes this component. Use core/datastore/postgres on its RDS Recipes, the application running CREATE EXTENSION vector in its database; vector-store sockets do not admit it, as nothing the build sees enables the extension.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:89f7d967c4cd85f0d2580c187330c84d304d1ad806488f725a3b698f21c3fbca
Publicado
2026-11-10T10:11:02Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:a37dcb2454ced0e154e7ad4f9950f74284503035f55d397c2dd3cf039c2c4214

Referencia en esta versión

oci://hub.aggrega.ai/component/core/datastore/pgvector:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
databasestringappdbnoLogical database name created on startup (POSTGRES_DB), with the vector extension enabled in it.
userstringappusernoBootstrap superuser role created on startup (POSTGRES_USER), owner of the initial database.
encodingstring—noDatabase encoding passed to initdb (e.g. UTF8). Omit to use the image default.
localestring—noDatabase locale passed to initdb (e.g. en_US.utf8). Omit to use the image default.
custom_configstring—noRaw server configuration block (postgresql.conf format), applied as the server's configuration file in place of the image's own, so a setting it omits takes the server's built-in default. listen_addresses is the one worth naming: its built-in default accepts local connections only, so a block for a server other workloads reach sets it, for example listen_addresses = '*'. The listen port comes from infra.port; a port setting here takes precedence and moves the server off the port the component publishes.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1024, max 65535)5432noServer listen port. Most operators should omit this and let the Recipe assign the default (5432). Every Recipe hands it to the server as its own port, so the server, its health checks and the published address all follow it.
engine_versionstring0.8.7-pg18-trixienoTag of the pgvector/pgvector image the Recipes run. One compound coordinate carries three parts: the extension version, the PostgreSQL major version it is built for, and the Debian release it is built on — so an operator supplies a value shaped like 0.8.7-pg18-trixie rather than a bare major version, for which the image publishes no tag. The build halts on a value naming no PostgreSQL major, or a major below 18, because the Recipes keep the data where the PostgreSQL 18 and later builds place it.
computeobject—no—
storageobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síAddress a client opens its database connection to. On Kubernetes it is the Service's DNS name, and on Compose the service name.
portinteger—síTCP port the server accepts connections on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming 5432.
userstring—noName of the login role a consumer authenticates as. The matching password arrives through the credential attached to the component, never through this contract.
databasestring—noName of the logical database created at startup, the one the vector extension is enabled in. A consumer names it in its connection string to land in the right database rather than the server's default.
protocolstring—noWire protocol the published address speaks — `postgres`, so a consumer stores and queries vectors with an ordinary PostgreSQL driver.
endpointstring—noConnection URI of the component's database, postgresql://<user>@<host>:<port>/<database>, for a consumer that takes one address rather than its parts. It carries no password, which arrives through the credential attached to the component. The user and the database are written into it as given, so a name holding a character a URI reserves, such as @, : or /, breaks it.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

No se declararon sockets uses.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

SlotSelectorObligatorioInyecciónSensibleDescripción
passwordfeature.aggrega.ai/kind=secretnoenvsíOptional database password credential. When attached, supplies POSTGRES_PASSWORD via the credential subsystem. Unattached, compose/pgvector and helm/pgvector set POSTGRES_PASSWORD to the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password.

Lista de permitidos de autoinyección

env

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Esta entidad no usa nada del catálogo.

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad