Josh Kupershmidt <schmiddy@gmail.com> writes:
> It's possible that the next 9.1 point release (9.1.2) would contain
> this fix, but I haven't verified this (the way to check would be to do
> a git checkout of the 9_1_STABLE branch from git, and see if the fix
> is present there).
No, it's not in any stable branch. It seemed like enough of a
behavioral change to be too risky to put into minor releases.
regards, tom lane
