Currently, the stage pessimistically assumes that any secondary index change during multi-update might lead to the Halloween problem, even if the changed index isn't used to scan the records (see `_updatedRecordIds` in UpdateStage). In most cases it means that if an update affects a secondary index, record ids of all updated records are temporarily stored by the stage, which might be quite a lot for some kinds of updates.