Vector Store Orchestrator¶
Vector Store Orchestrator embeds and stores documents in a PostgreSQL collection for semantic search. Use it during ingestion, then connect a Retriever Provider to the same collection when an Agent needs to search those documents.
- Category: VectorStore
- Purpose: Stores embedded documents in PostgreSQL and makes them searchable. Manages the database schema, indexes, and optimisation automatically
- Inputs:
documents- Documents to storeembedder- Embedding provider connection- Outputs:
result- Storage result - Configuration — Data:
- Select Credential: PostgreSQL connection (required)
- Collection Name: Separates one data set from another (required). Distinct collections keep unrelated documents from mixing in search results
- Table Prefix (Optional): Full database isolation for separate projects or tenants
- Configuration — Metadata:
- Custom Metadata: Labels applied to every stored document, as JSON. Used later as search filters
- Preserve Document Metadata: Default on. Keeps the document's own metadata such as source URL and chunk index. Required for answering "where did this come from"
- Metadata Strategy:
merge(combine, custom wins on conflict),replace(custom only),document_only. Defaultmerge - Configuration — Search:
- Search Algorithm:
cosine(angle between vectors — the standard for text),euclidean(straight-line distance),inner_product. Defaultcosine - Search K: 1–50, default 10. Number of results returned
- Score Threshold: 0.0–1.0, step 0.1, default 0.0. Minimum similarity required
- Batch Size: 10–1000, step 10, default 100. Write batch size
- Pre Delete Collection: Default off. When enabled, the collection is wiped on every run before writing. Useful during testing, destructive in production
- Enable HNSW Index: Default on. Speeds up vector search significantly at the cost of a little extra storage
- Usage: Requires the
pgvectorextension. Standard PostgreSQL images do not include it.