Re: tolower() identifier downcasing versus multibyte encodings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, "Francisco Figueiredo Jr(dot)" <francisco(at)npgsql(dot)org>
Subject: Re: tolower() identifier downcasing versus multibyte encodings
Date: 2011-03-19 15:05:41
Message-ID: 12444.1300547141@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marko Kreen <markokr(at)gmail(dot)com> writes:
> On Sat, Mar 19, 2011 at 6:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-03-19 15:24:14 Re: Indent authentication overloading
Previous Message Nikhil Sontakke 2011-03-19 14:46:48 Re: VACUUM FULL deadlock with backend startup