YES BOIIIZ
Thanks to the man of the night @pfigel
The problem wasn't the lock, but the constraints : https://mastodon.at/@pfigel/98851844229832651
https://mstdn.io/media/fhbswyFxf-Bgynj2uzI https://mstdn.io/media/nDiNYAziV6HEGwb4zQQ
@angristan glad it worked!
@aschmitz any idea what might have gone wrong here? https://hastebin.milkywan.xyz/iseruyikob.sql
@pfigel @angristan To hazard a guess, the terminal output there looks like it was a resumed migration that failed between adding the new foreign constraints to the column and dropping the old one. That's not a place the migration says it's safe to kill it (because it's not), but we could probably handle that a bit better (by removing the constraints ourselves).
@angristan @pfigel (To be clear, it looks like you're in a safe state, just that it died in a pretty difficult to recover from section. Removing the foreign keys and re-running it as you did should fix that specific problem, though.)
@angristan KEEP FIGHTING BRO! KEEP PUSHING!