The fix that was implemented in db-control enables the row movement when needed. While I agree that we should be consistent and have row movement enabled in all tables, unless we have some sanity check which will test our schema definitions, even if we fix this bugzilla once, the problem may reoccur. Therefore I feel that the db-control fix is actually enough.
First of all, db-control will work for embedded databases only. Second of all, closing the bug just because there's no sanity test for this available is nothing but a shallow argument. Besides, if you think having a sanity test like that is important, it can be implemented as a part of the fix for this bug. I'm reopening this bug and assigning it to myself, since I don't consider discussions about what the current default owner of 'Server' component "feels" that constructive (or important).