Is there a way to put the migrations table in a specific schema in postgres?

[kingsleyh]

I have one postgres database with mutliple schemas and I want to apply migrations to each schema independently. At the moment when I create a migration the migrations tracking table goes in the main db area - but this means that if I have 2 microservices each using one of the schemas - the migrations get stored in one table for both schemas.

I would like to separate it so that each microservice connects to a schema in the same db and the migrations are for each are separately living in the corresponding schema rather than a single location shared by all schemas.

Hope that makes sense - maybe it's already possible I just don't know how.

[kingsleyh]

hmm maybe it would work if I make a user per schema that has access to only that schema and then use that user in the database_url var?

[kingsleyh]

nope doesn't work - seems it always put the migrations table in the public schema - I've switched to using refinery for migrations because that allows to specify which schema and table name to use to store the migrations.