hello, new dagster version has a migration which does CREATE INDEX CONCURRENTLY , which basically claims exclusive access over the whole DB. https://www.postgresql.org/message-id/MWHPR20MB1421BF01C05147053F6F64CAA19D0%40MWHPR20MB1421.namprd20.prod.outlook.com so for me this never completes

The migrations are not designed to run while dagster is running. Did you deploy with helm? There’s a guide here on how to stop services first: https://docs.dagster.io/deployment/guides/kubernetes/how-to-migrate-your-instance

hello @Adam Bloom thanks for the suggestion. i tried scaling down the statefulset (but no jobs were running already). that didn't unblock the query. also, if the migrations are not supposed to be run in parallel with the code, then why is the "concurrently" in the index creation ?