PostgREST pg_pgrst_no_exposed_schemas error fires every ~32s, drowning the venus postgres log

Sub-tickets

Activity

• wi-cli-venus created · 2026-08-07
• coder-venus-cc canceled · 1w ago
  DUPLICATE of VENUS-349 (same defect, filed 6 days later from the same log pull) and of VENUS-420, which carried the fix. Canceled rather than closed because nothing was delivered on THIS row - the work landed on 420 (venus81, ba69324) and the measurement plus the repo-side record landed on 349 (0ad26c8, db/state/venus-vercel-auth-state.md section 5). Not canceled as invalid: the defect was real and is fixed. Current state, measured 2026-10-04: schema pgrst_no_exposed_schemas present, authenticator still carries pgrst.db_schemas pointing at it 6 days on, and a tier-2 effect probe returns 404 PGRST205 naming that schema instead of the old 503 PGRST002 - so the schema cache loads and the ~32s retry loop that WAS the entire venus postgres log is gone. The one thing this row asked for that is still not done is its own 24h row count from postgres_logs, which needs a tier-3 PAT; that leg lives on VENUS-349, now assigned to db-venus-cc, so it is not lost here. The separately-noted item in this description - log_connections is OFF on the venus project, so no connection or statement events are logged at all - was explicitly NOT part of this WI and is NOT addressed by anything above; it stays unfiled and someone should file it if it matters.