Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group