any idea what would cause a migration to randomly try to rename all of my indexes?

You have probably upgraded from prisma 2.x to prisma 3.x and hitting named constraints breaking change. More info: https://www.prisma.io/docs/guides/upgrade-guides/upgrading-versions/upgrading-to-prisma-3 https://www.prisma.io/docs/guides/upgrade-guides/upgrading-versions/upgrading-to-prisma-3/named-constraints/

I’ve been on 3 for a while now though

Maybe it's your first migration? Not sure but looking at your SQL, those index names are pre 3.x and 3.x (after RENAME). So I would look at those links I've sent you

weird ok

Hey Mischa - we are thinking about releasing some additional commands in migrate to help with diffing (prisma schema|migrations history|database schema). If that sounds interesting please take a look at the proposal and leave a like or comment: https://github.com/prisma/prisma/issues/10561

I don’t have a great way to run migrate commands inside my VPC right now sadly, I’m trying to do it with lambdas

ok, let us know how it goes with the lambdas!