It is intended that
all transactions should be ended by rollback for innodb_fake_changes=ON.
As transactional RDBMS, any fake commit should not be allowed.
For safeness, all commit are treated as error, for now.
(technical reason: fake change doesn't cause any logs and we cannot distinguish modifying transaction by whether the transaction has modified logs or not.)
Thinking the objective of the function "for mksp+ ?",
it should not be problem.
It is intended that fake_changes= ON.
all transactions should be ended by rollback for innodb_
As transactional RDBMS, any fake commit should not be allowed.
For safeness, all commit are treated as error, for now.
(technical reason: fake change doesn't cause any logs and we cannot distinguish modifying transaction by whether the transaction has modified logs or not.)
Thinking the objective of the function "for mksp+ ?",
it should not be problem.
This behavior is not bug, I intended.