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> |
||
|---|---|---|
| .. | ||
| changing-embeddings.mdx | ||
| configuration.mdx | ||
| guidelines.mdx | ||
| license.mdx | ||
| self-hosting.mdx | ||
| troubleshooting.mdx | ||