Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem

> 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.

The locale check is near the bottom of parser/gram.y, so you can
certainly enable indexing there.

I am told that french does not have 255 as it's max character, and there
there is no collating interface to request the highest character. I
suppose one hack would be to go out and test all the char values to see
which is highest.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026