Bug 26744 implemented logging for patron extended attributes. If a patron is in a batch import and the attributes are the same, it logs a change even if nothing else changed, thus making the patron logs large and unhelpful. This can be a problem for academic libraries who have automated loading processes to sync patron with their academic systems. Maybe could use the diff, if diff o=n don't log?
We are in this situation. Aside from a huge number of unnecessary log entries for the deleted/readded attributes, the entry is misleading to a staff member trouble-shooting on a patron who doesn't understand the quirk, and it blinds us on actual changes to a patron's attributes. Logging attribute changes is great but we only want to see actual changes.