Question
Answer
If you face a timeout error with a context of postgres advisory lock (SELECT pg_advisory_lock(72707369)), try running it again. If the error persists, it's just a warning. Make sure that the current rows consisting of `idReferral` already contain a unique value. If you apply a unique constraint, you might get a warning saying that the migration will fail if there are existing duplicate values.
Arun Kumar
07/13/2021, 11:52 AMprisma migrate div
Context: Timed out trying to acquire a postgres advisory lock (SELECT pg_advisory_lock(72707369)). Elapsed: 10000ms. See
<https://pris.ly/d/migrate-advisory-locking> for details.
Nick
07/13/2021, 11:53 AMArun Kumar
07/13/2021, 12:02 PMArun Kumar
07/13/2021, 12:05 PM• A unique constraint covering the columns `[idReferral]` on the table MyTable will be added. If there are existing duplicate values, this will fail.
Nick
07/13/2021, 12:13 PMidReferral
already contain a unique value.Nick
07/13/2021, 12:14 PM