If schema changes are allowed while a primary key change is in progress, all existing schema change setup logic needs to "understand" when a primary key change is happening and set up the target table descriptor as if the primary key change has been completed. The surface area on this task is quite large, and it would be better to disable the feature until the scope is more clear and each case is handled.