That's because this entire approach is broken: if one cannot afford to bring database down to do alter table migration, one should always go a lazy migration ei

That's because this entire approach is broken: if one cannot afford to bring database down to do alter table migration, one should always go a lazy migration either via application stack using write-to-new only, read from new on miss, read from old, followed by a backfill or using triggers.