Is there a way to write to a GOOSE_TABLE in another Redshift database from where migrations are run?

[andrew-sadoway]

I’m trying to run SQL migrations on a Redshift database (db123), which is read-only. However, I need to grant SELECT permissions to users in Goose using a migration script.

By default, Goose stores its state table in the same database where migrations are executed. Since db123 is read-only, that setup won’t work.

Is there a way to configure Goose to track migration state in a table located in a different database (using a separate connection string)?

[mfridman]

Short answer is no, the schema version table is stored in the same database.

Interesting use case though, I've never heard of this case.

[andrew-sadoway]

Got it. Thanks for the quick reply.