From f840b7ca9ba956a3bf81e393277a3994e8d3d5ba Mon Sep 17 00:00:00 2001 From: Vasyl Vdovychenko Date: Wed, 17 Jun 2026 11:15:37 -0400 Subject: [PATCH] fix(ops): backup verify uses pgvector image (restore was failing 6 days) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- infra/scripts/backup-verify.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infra/scripts/backup-verify.sh b/infra/scripts/backup-verify.sh index 84f9a0c7..55a8c606 100755 --- a/infra/scripts/backup-verify.sh +++ b/infra/scripts/backup-verify.sh @@ -32,7 +32,7 @@ docker run -d --rm \ -e POSTGRES_PASSWORD="$PG_PASS" \ -e POSTGRES_DB="$PG_DB" \ -p "$PORT:5432" \ - postgres:16 >/dev/null + pgvector/pgvector:pg16 >/dev/null # prod schema uses CREATE EXTENSION vector (pgvector); vanilla postgres:16 fails restore echo "[verify] waiting for postgres to accept connections ..." for i in {1..30}; do