cd62ae1737
The previous deploy of c4f6cc1 failed because I had applied the timings
column manually via psql before the deploy ran, leaving the hash-based
migrate runner with raw ADD COLUMN that conflicts with the existing column.
Hash differs after this change so the runner will retry on next deploy
and succeed (no-op on the already-applied column, success path records
the hash).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 line
66 B
SQL
1 line
66 B
SQL
ALTER TABLE "query_logs" ADD COLUMN IF NOT EXISTS "timings" jsonb; |