Bu sayfa makine çevirisiyle çevrilmiştir. İngilizce aslını okuyun.

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.

Köken

ResmiBu kataloğun resmi yayıncı olarak tanıdığı bir imzalama kimliğiyle imzalanmıştır.
İçerik özeti
sha256:89f7d967c4cd85f0d2580c187330c84d304d1ad806488f725a3b698f21c3fbca
Yayımlanma
2026-11-10T10:11:02Z
İmzalama kimliği
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

İmza

  • Resmiapplication/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

Bu sürümdeki referans

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

Geliştirici parametreleri

Geliştiricinin Aggregate'te ayarladığı değerler.

AdTipVarsayılanZorunluAçıklama
databasestringappdbhayırLogical database name created on startup (POSTGRES_DB), with the vector extension enabled in it.
userstringappuserhayırBootstrap superuser role created on startup (POSTGRES_USER), owner of the initial database.
encodingstring—hayırDatabase encoding passed to initdb (e.g. UTF8). Omit to use the image default.
localestring—hayırDatabase locale passed to initdb (e.g. en_US.utf8). Omit to use the image default.
custom_configstring—hayırRaw 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.

Operatör boyutlandırması

Operatörün her ortam için ayarladığı altyapı boyutlandırması.

AdTipVarsayılanZorunluAçıklama
portinteger (min 1024, max 65535)5432hayırServer 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-trixiehayırTag 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—hayır—
storageobject—hayır—
overridesobject (open)—hayırProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Çıktı sözleşmesi

Bu bileşenin uses topolojisi üzerinden tüketicilere yayımladığı değerler.

AdTipVarsayılanZorunluAçıklama
hoststring—evetAddress a client opens its database connection to. On Kubernetes it is the Service's DNS name, and on Compose the service name.
portinteger—evetTCP 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—hayırName of the login role a consumer authenticates as. The matching password arrives through the credential attached to the component, never through this contract.
databasestring—hayırName 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—hayırWire protocol the published address speaks — `postgres`, so a consumer stores and queries vectors with an ordinary PostgreSQL driver.
endpointstring—hayırConnection 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.

Uses soketleri

Bu bileşenin üzerinden bağlandığı bağımlılık soketleri. Bir soket üzerinden kurulan her bağlantının hedefi, soketin etiket seçicisini karşılamalıdır ve her bağlantı, soketin bildirdiği yuvalarda bir ek taşıyabilir. Aggregate'in veya Release'in soket üzerinden kurduğu her bağlantı, zorunlu bir yuvayı doldurmakla yükümlüdür.

uses soketi bildirilmemiş.

Ekleme yuvaları

Bir Feature'ın bu bileşene eklendiği adlandırılmış bağlama noktaları. Bir yuvanın seçicisi, onu hangi Feature'ın doldurabileceğini sınırlar ve inject listesi, Feature'ın malzemesinin nasıl iletilebileceğini belirtir. Zorunlu bir yuva, her örnekte, örnek üzerindeki veya onun üstündeki bir kapsamdaki bir ek aracılığıyla bağlanmalıdır, hassas bir yuva ise gizli malzemeyi işlemek üzere bildirilmiştir. Bir Feature, hiçbir yuvanın bildirmediği bir ad altında da eklenebilir.

YuvaSeçiciZorunluEnjeksiyonHassasAçıklama
passwordfeature.aggrega.ai/kind=secrethayırenvevetOptional 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.

Kendi kendine enjeksiyon izin listesi

env

İlişkiler

Diğer yayımlanmış varlıklara giden ve onlardan gelen tipli kenarlar. Yayımlanmış bir hedefi olmayan bir başvuru, bağlantı yerine kopuk bir kenar olarak gösterilir.

Kullanır

Bu varlık katalogdaki hiçbir şeyi kullanmaz.

Kullananlar

Component kavram başvurusu →

Aggrega kataloğu — bileşenlerin, özelliklerin, tariflerin ve bunları oluşturan eklentilerin açık bir dizini.

Ortak Aggrega tasarım sistemiyle oluşturuldu.

Gizlilik