Bruce,
This is extremely bad news, because if will make PostgreSQL 6.5 unusable for
most of my applications. Perhaps something can be done to resolve this
situation?
I understand the problem for 16-bit characters support, but for most of the
encodings that support only 8 bit characters it should be safe to assume the
maximum character value is 255.
Anyway, making this check compile-time defined would certainly fix things
here, because in my case the cyrillic letters order match that of the binary
encoding (that is, the first alphabet letter is before the second etc).
Perhaps the locale data can be used to gather this information?
I will do some testing without using locale to see what happens.
Regards,
Daniel
>>>Bruce Momjian said:> > Yes,> > > > I do build with --enable-locale, but I do not build with --enable-mb and d o >
>not use client_encoding or server_encoding.> > > > The content of the keys is in cyrillic. I have LC_CTYPE=CP1251 in
the> > environment in both server and client, and this has worked for me in 6.4.2 .> > > This certainly explains it.
With locale enabled, LIKE does not use> indexes because we can't figure out how to do the indexing trick with>
non-ASCIIcharacter sets because we can't figure out the maximum> character value for a particular encoding.> > We
didn'tdo the check in 6.4.*, and LIKE was not returning the proper> results for queries at those sites that used
locale.>> -- > Bruce Momjian | http://www.op.net/~candle> maillist@candle.pha.pa.us
| (610) 853-3000> + If your life is a hard drive, | 830 Blythe Avenue> + Christ can be your backup.
| Drexel Hill, Pennsylvania 19026