Michael Paquier <michael@paquier.xyz> writes:
> At the end, no need to do that. I have been able to hack the
> attached, that shows the difference of treatment for \v when running
> in macOS. Evan, what do you think?
FWIW, I think the status quo is fine. Having hstore do something that
is neither its historical behavior nor aligned with the core parser
doesn't seem like a great idea. I don't buy this argument that
somebody might be depending on the handling of \v in particular. It's
not any stronger than the argument that they might be depending on,
say, recognizing no-break space (0xA0) in LATIN1, which the old code
did (probably, depending on platform) and scanner_isspace will not.
If anything, the answer for these concerns is that d522b05c8
should not have been back-patched. But I'm okay with where we are.
regards, tom lane
