Re: Unicode upper() bug still present - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Unicode upper() bug still present
Date
Msg-id Pine.LNX.4.44.0310201957190.29086-100000@peter.localdomain
Whole thread Raw
In response to Re: Unicode upper() bug still present  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unicode upper() bug still present
Re: Unicode upper() bug still present
List pgsql-hackers
Tom Lane writes:

> I noticed by chance that glibc has a "reentrant locale" API that seems
> to allow for efficient access to multiple locales concurrently.  Perhaps
> it would be a reasonable solution to support multiple locales only on
> machines that have this library.  If we have to write our own locale
> support it's likely to be a long time coming :-(

Naturally, I cannot promise anything, but this is at the top of my list
for the next release.  I already have sorted out the specifications and
algorithms and collected locale data for most corners of the world, so
it's just the coding left.  Unfortunately, a real, sustainable fix of this
situations requires us to start at the very bottom, namely the character
set conversion interface, then the gettext interface, then the new locale
library, then integrating the per-column granularity into the
parser/planer/executor.  So you may be looking at a two-release process.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Unicode upper() bug still present
Next
From: Hannu Krosing
Date:
Subject: Re: Unicode upper() bug still present