Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Evan Jones <evan(dot)jones(at)datadoghq(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific
Date: 2023-06-18 16:38:12
Message-ID: 2765603.1687106292@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2023-06-18 16:45:32 Re: Do we want a hashset type?
Previous Message jian he 2023-06-18 13:23:22 Re: Deleting prepared statements from libpq.