4 ms·
> That shouldn't be a big issue. Any service large/complex enough to care does the schema upgrades in phases, so it's 1. Make code future compatible. 2. Migrate
by gigatexal 3y ago
> That shouldn't be a big issue. Any service large/complex enough to care does the schema upgrades in phases, so it's 1. Make code future compatible. 2. Migrate data. 3. Remove old schema support.
Exactly this, schema migrations should be an append, deprecate, drop operation over time.
- rockwotj 3y agoI wish there were ways to enforce this on the db so you never accidentally grabbed a table lock during these operations. definitely have shot myself in the foot with postgres on this
- ddorian43 3y ago> I wish there were ways to enforce this on the db so you never accidentally grabbed a table lock during these operations. You can use a linter for PostgreSQL migrations https://squawkhq.com/ https://squawkhq.com/