#18068
Since this background update takes the maximum stream ordering on its first iteration (assuming that rows after that will be populated at insertion time), it's not safe to either roll back, or to start the background update before all other writing workers have been upgraded.
This goes against our rollback policy — the SCHEMA_COMPAT_VERSION should be adjusted to reflect this, but even still, as a matter of principle we 'shouldn't' ship a version without at least one version of rollback ability.
This also goes against our (unstated, but relied upon) policy of letting you upgrade workers one by one. We usually require upgrade notes to be written when we can't meet this aspect.
#18068
Since this background update takes the maximum stream ordering on its first iteration (assuming that rows after that will be populated at insertion time), it's not safe to either roll back, or to start the background update before all other writing workers have been upgraded.
This goes against our rollback policy — the
SCHEMA_COMPAT_VERSIONshould be adjusted to reflect this, but even still, as a matter of principle we 'shouldn't' ship a version without at least one version of rollback ability.This also goes against our (unstated, but relied upon) policy of letting you upgrade workers one by one. We usually require upgrade notes to be written when we can't meet this aspect.