search

timgit / pg-boss

Queueing jobs in Postgres from Node.js like a boss
MIT License
2.07k stars 157 forks source link

Feature/Questions Request related to getMigrationPlans + getRollbackPlans #337

Closed semaurer closed 2 years ago

semaurer commented 2 years ago

Hey, not sure if I missed it but would it be possible to add a config option to the PG Boss instantiation that says do not upgrade the DB schema version (and if it has to upgrade because it will error, it could throw some error stating that you must upgrade)?

Some Context: I'm using PG boss in a situation where my db user does not have create privileges in prod and am currently trying to upgrade from 5.2.3 (db schema version 16) to the current latest 7.4.0 (db schema version 20). I am trying to get the migrationPlans for each version to upgrade our db manually. It doesn't seem like I'm able to use getMigrationPlans because when pgBoss starts up it auto upgrades the DB from 16 -> 20.

I was able to get around this by just commenting out the source code in pg-boss where it updates (but could be nice to pass it as a config option)

semaurer commented 2 years ago

Not sure what was happening, but getMigrationPlans appears to be working now so can disregard this. Originally I kept having issues with "version not found"