Re: Latest on CITEXT 2.0

Поиск
Список
Период
Сортировка
Искать
От
Marko Kreen
Тема
Re: Latest on CITEXT 2.0
Дата
Msg-id
e51f66da0807010813i6aec31bp7dc37419d5964679@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
Re: Latest on CITEXT 2.0 Martijn van Oosterhout <kleptog@svana.org>
Re: Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
Re: Latest on CITEXT 2.0 Tom Lane <tgl@sss.pgh.pa.us>
Re: Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
Re: Latest on CITEXT 2.0 Tom Lane <tgl@sss.pgh.pa.us>
Re: Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
Re: Latest on CITEXT 2.0 "Marko Kreen" <markokr@gmail.com>
Re: Latest on CITEXT 2.0 Tom Lane <tgl@sss.pgh.pa.us>
Re: Latest on CITEXT 2.0 "Marko Kreen" <markokr@gmail.com>
Re: Latest on CITEXT 2.0 Tom Lane <tgl@sss.pgh.pa.us>
Re: Latest on CITEXT 2.0 Bruce Momjian <bruce@momjian.us>
Re: Latest on CITEXT 2.0 "Marko Kreen" <markokr@gmail.com>
Re: Latest on CITEXT 2.0 Tom Lane <tgl@sss.pgh.pa.us>
Re: Latest on CITEXT 2.0 "Marko Kreen" <markokr@gmail.com>
Re: Latest on CITEXT 2.0 Alvaro Herrera <alvherre@commandprompt.com>
Re: Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
Re: Latest on CITEXT 2.0 Josh Berkus <josh@agliodbs.com>
Re: Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
Re: Latest on CITEXT 2.0 Josh Berkus <josh@agliodbs.com>
Re: Latest on CITEXT 2.0 "David E. Wheeler" <david@kineticode.com>
On 7/1/08, Tom Lane  wrote:
> "Marko Kreen"  writes:
>  > On 6/26/08, Tom Lane  wrote:
>
> >> BTW, I don't think you can use that same-length optimization for
>  >> citext.  There's no reason to think that upper/lowercase pairs will
>  >> have the same length all the time in multibyte encodings.
>
>  > What about this code in current str_tolower():
>
>  >         /* Output workspace cannot have more codes than input bytes */
>  >         workspace = (wchar_t *) palloc((nbytes + 1) * sizeof(wchar_t));
>
>
> That's working with wchars, not bytes.

Ah, I missed the point of char2wchar() line.

I'm rather unfamiliar with various MB API-s, sorry.

There's another thing I'm probably missing: does current code handle
multi-wchar codepoints?  Or is it guaranteed they don't happen?
(Wasn't wchar_t usually 16bit value?)

-- 
marko

В списке pgsql-hackers по дате отправления
От: Radek Strnad
Дата:
От: Richard Huxton
Дата:
FAQ