Support for running migrations to different schemas in same database in parallel #3476
Description
Currently, a fixed name is used for the migration lock (advisory lock in PG). In applications using a single DB and separate schema for each microservice, this is causing problems when migrations are run. One microservice running a lengthy migration will block other microservices from checking and running their migrations.
It should be possible to run the migrations to different schemas in parallel.
The issue has been discussed also in this PR: #3475