From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Don't downcase non-ascii identifier chars in multi-byte encoding |
Date: | 2013-06-08 14:25:00 |
Message-ID: | E1UlK4i-00067B-Gq@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Don't downcase non-ascii identifier chars in multi-byte encodings.
Long-standing code has called tolower() on identifier character bytes
with the high bit set. This is clearly an error and produces junk output
when the encoding is multi-byte. This patch therefore restricts this
activity to cases where there is a character with the high bit set AND
the encoding is single-byte.
There have been numerous gripes about this, most recently from Martin
Schäfer.
Backpatch to all live releases.
Branch
------
REL8_4_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/160f2cb4ec56251751bf778af8a9d579befb0059
Modified Files
--------------
src/backend/parser/scansup.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2013-06-08 14:25:15 | pgsql: Don't downcase non-ascii identifier chars in multi-byte encoding |
Previous Message | Andrew Dunstan | 2013-06-08 13:21:20 | pgsql: Handle Unicode surrogate pairs correctly when processing JSON. |