We just had a weird experience that i dont understand: 1. We ran migrate deploy (adding a

@unique

) through pgbouncer as we always do (and it usually works well) 2. The migrate failed because we had duplicate entries 3. We removed the duplicate entries and re-ran migrate deploy 4. Then we saw

Error querying the database: db error: ERROR: relation "_prisma_migrations" already exists

5. We deleted the failed migration from the table and re-ran migrate deploy 6. Still the same error from 4. 7. We ran migrate deploy directly against the database (no pgbouncer) and this worked! We solved it, but I thought maybe this helps someone, so there it is.

Thanks for sharing Sven. Which mode is PgBouncer running in? Can you share the contents of the generated migration adding @unique?