From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "kolmyk(at)hotmail(dot)com" <kolmyk(at)hotmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #8385: greek symbols as function name |
Date: | 2013-08-18 20:48:21 |
Message-ID: | 1376858901.88877.YahooMailNeo@web162902.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
>> It occurs to me that the behavior you are seeing would be
>> consistent with 945 being considered an uppercase letter, with
>> 60536 being considered its lowercase form. Normal PostgreSQL
>> case-folding of identifiers would then cause exactly the symptoms
>> you are seeing.
>
> Hmm ... identifier case-folding isn't really supposed to do anything to
> multibyte characters. I wonder if this isn't a variant of the issue
> recently fixed in commit d535136b5d60b19f7ffa777b97ed301739c15a9d.
Maybe. I notice that if you interpret the first byte as a Unicode
code point (as opposed to the first byte of a UTF-8 encoded
character), it is an uppercase letter. But I can't quite see how
that gets to the decimal 60536 value. Also, going to a commit
prior to the referenced fix I still don't see any problem on my
machine. That doesn't rule out a platform-specific manifestation
of the issue, though.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-08-19 07:24:27 | Re: BUG #8294: new timeline 6 forked off current dat abase system timeline 5 before current recovery point 0/100000 |
Previous Message | Tom Lane | 2013-08-18 18:40:35 | Re: BUG #8385: greek symbols as function name |