Tom Lane <t...@sss.pgh.pa.us> wrote: > Kevin Grittner <kgri...@ymail.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
