>> I can't see a reason to /not/ fix something this simple for the 7.2 >> release.
Seems like a safe fix to me too.
regards, tom lane