fix(ops): backup verify uses pgvector image (restore failing 6 days)#350
Merged
Conversation
The daily backup workflow's verify step (restore the dump into a throwaway Postgres + sanity-query it) spun up vanilla postgres:16. Since the pgvector work (Phase 4 embeddings), the schema dump contains 'CREATE EXTENSION vector', which vanilla postgres:16 can't load: ERROR: extension "vector" is not available [verify] FAIL: restore aborted on error → the verify gate failed every night since 2026-06-12, marking the whole backup workflow red. Fix: the throwaway verify container now uses pgvector/pgvector:pg16 (the same image prod runs), so the dump restores. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backups have been red since 2026-06-12
The daily
backup.ymlworkflow does: dump → verify (restore the dump into a throwaway Postgres + run sanity queries). The verify container was vanillapostgres:16. Since the pgvector work (Phase 4 embeddings,chapter_chunkvectors), the schema dump containsCREATE EXTENSION vector, which vanillapostgres:16can't load:→ the verify gate failed every night for 6 days, marking the whole backup workflow failed.
Fix
infra/scripts/backup-verify.sh— the throwaway verify container now usespgvector/pgvector:pg16(the same image prod runs) instead ofpostgres:16, so the dump (withCREATE EXTENSION vector) restores cleanly. One-line image swap.bash -nclean. After merge I'll triggerbackup.ymlviaworkflow_dispatchto confirm it goes green.🤖 Generated with Claude Code