Re: BUG #14662: 'has_table_privilege()' function fails with error, "invalid name syntax" when using Japanese symbols

From: Justin Muise <JMuise(at)esri(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14662: 'has_table_privilege()' function fails with error, "invalid name syntax" when using Japanese symbols
Date: 2017-05-22 21:12:20
Message-ID: a275f08a973349e58dbf34000a77038c@RED-INF-MXMB-P1.esri.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

Just wanted to see if here was any additional information/testing you required from me, and if you are still reviewing this issue.

Thanks,

Justin

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, May 19, 2017 10:44 AM
To: Justin Muise <JMuise(at)esri(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #14662: 'has_table_privilege()' function fails with error, "invalid name syntax" when using Japanese symbols

Justin Muise <JMuise(at)esri(dot)com> writes:
> Thank you for your quick response! Please see the attached image.

Hm. If I'm reading that correctly, you've got encoding set to UTF8 but the OS is going to think the encoding is WIN1252, which will likely affect the behavior of isspace(), which'd successfully break this function. I'm not sure how the system allowed you to do that.

I wonder though whether it wouldn't be better for SplitIdentifierString to use scanner_isspace() rather than isspace(). That would cause it to not treat things like &nbsp; as whitespace, but maybe that's OK.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Emre Hasegeli 2017-05-23 08:27:30 Re: BUG #14637: Tests fail with pl_PL.UTF-8 locale
Previous Message Andres Freund 2017-05-22 15:42:27 Re: [HACKERS] Concurrent ALTER SEQUENCE RESTART Regression