How do we safely roll back a Prisma database migration that locked our production Postgres table fifteen minutes ago?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do we safely roll back a Prisma database migration that locked our production Postgres table fifteen minutes ago?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Prisma migrate deploy production failed migration prisma migrate resolve rolled back docs PostgreSQL advisory locks Google ↗
PostgreSQL official documentation pg_blocking_pids pg_stat_activity lock monitoring Google ↗
- prisma migrate resolve | Fix Migration History Issues · docs.prisma.io
- Patching & hotfixing (Prisma ORM v7) · prisma.io
- Rollbacks and recovery in Prisma ORM · prisma.io
- web/apps/docs/content/docs/orm/v7/prisma-migrate/workflows/development-and-production.mdx at main · prisma/web · github.com
- New tables missing after a deploy? How to run database migrations safely in production · prisma.io
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Prisma migrate deploy production failed migration prisma migrate resolve rolled back docs PostgreSQL advisory locks OBSERVED | Google ↗ AI Mode ↗ | — | Consequence | — | — | 1x of 1 | |
PostgreSQL official documentation pg_blocking_pids pg_stat_activity lock monitoring OBSERVED | Google ↗ AI Mode ↗ | — | Consequence | — | — | 1x of 1 |