d191c107e5
* docs: document pgvector preinstall for least-privilege DB roles Honcho issues CREATE EXTENSION IF NOT EXISTS vector before migrations and again at server startup, both using the DB_CONNECTION_URI role. On deployments where that role deliberately cannot create extensions (managed Postgres, Kubernetes operators, NixOS), both statements fail with a privilege error — IF NOT EXISTS does not save you, because Postgres checks the privilege before checking for the extension. Document preinstalling pgvector as a privileged role as the supported path, and add a troubleshooting entry keyed to the exact error string. Note that docker compose is unaffected, since the bundled database service creates the extension via an initdb script. Refs #614 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs: clarify why docker compose avoids the pgvector privilege error The previous wording pinned the claim entirely on database/init.sql, which only runs on first boot of an empty data volume. The load-bearing reason is that the bundled stack connects as the postgres superuser, so it can create the extension regardless of volume state. Name that first and keep init.sql as the secondary reason. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api-reference | ||
| contributing | ||
| documentation | ||
| guides | ||
| migrations | ||
| README.md | ||
| openapi.json | ||
README.md
This subdirectory contains the peer-paradigm documentation for Honcho (Honcho v2.0.0 onwards).