Mistral
Hosted embeddings through Mistral's API. The key stays in providers.d on the inference host (the database machine in embedded mode, each postvec-server in remote mode).
1. Add the provider
sudo postvec provider add mistral --model mistral-embed
postvec provider ls
sudo postvec doctor --database appThe command prompts for the key without echo, writes /etc/postvec/providers.d/mistral.toml (0600), probes the key with one embed call, reloads the host and refreshes postvec.models.
Expected
providers.d: /etc/postvec/providers.d
mistral (mistral, key: inline (redacted))
mistral-mistral-embed dim 1024 serveddoctor exits 0. The name is in postvec.models.
Built-in catalogue names:
--model | Name in SQL | Dim |
|---|---|---|
mistral-embed | mistral-mistral-embed | 1024 |
Pass --api-key-file PATH or --api-key-env VAR instead of the prompt. With --api-key-file the key stays in that file and provider ls reports file:PATH instead of inline.
Any other Mistral embedding id works. The probe measures the dimension, or --dim states it with --no-verify. --base-url fronts a Mistral-compatible origin.
2. Bind a column
SELECT postvec.enable('docs', 'body',
model => 'mistral-mistral-embed');
-- NOTICE: postvec: model "mistral-mistral-embed" is served by
-- external provider "mistral"; source text from column "body" will
-- be sent to that provider for embeddingExpected
docs.body_semantic is vector(1024). pending_jobs returns to 0.
SET postvec.query_timeout_ms = 10000;
SELECT postvec.create_vector_index('docs', 'body');
SELECT * FROM postvec.search('docs', 'body', 'revenue outlook', limit_n => 5);On postvec-server
Run the add on a postvec-server node. The CLI finds no local cluster there and writes <server-root>/providers.d, the directory that node serves from:
sudo postvec provider add mistral --model mistral-embed \
--acknowledge-in-use --yesCopy the same file onto every node, then reload each host. External providers covers keys, failures and moving a column off the provider.