Re: tolower() identifier downcasing versus multibyte encodings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tolower() identifier downcasing versus multibyte encodings
Date
Msg-id 12444.1300547141@sss.pgh.pa.us
Whole thread Raw
In response to Re: tolower() identifier downcasing versus multibyte encodings  (Marko Kreen <markokr@gmail.com>)
Responses Re: tolower() identifier downcasing versus multibyte encodings
List pgsql-hackers
Marko Kreen <markokr@gmail.com> writes:
> On Sat, Mar 19, 2011 at 6:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Or we could bite the bullet and start using str_tolower(), but the
>> performance implications of that are unpleasant; not to mention that
>> we really don't want to re-introduce the "Turkish problem" with
>> unexpected handling of i/I in identifiers.

> How about first pass with 'a' - 'A' and if highbit is found
> then str_tolower()?

Hm, maybe.

There's still the problem of what to do in src/port/pgstrcasecmp.c,
which won't have the infrastructure needed to do that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Nikhil Sontakke
Date:
Subject: Re: VACUUM FULL deadlock with backend startup
Next
From: Tom Lane
Date:
Subject: Re: Indent authentication overloading