Re: texteq/byteaeq: avoid detoast [REVIEW]
От | Itagaki Takahiro |
---|---|
Тема | Re: texteq/byteaeq: avoid detoast [REVIEW] |
Дата | |
Msg-id | AANLkTinB9=Yd_ci8=AZqOEk7Mr1Ze+L6k+ubpKbEbfoX@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: texteq/byteaeq: avoid detoast [REVIEW] (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: texteq/byteaeq: avoid detoast [REVIEW]
|
Список | pgsql-hackers |
On Mon, Jan 17, 2011 at 16:13, Pavel Stehule <pavel.stehule@gmail.com> wrote: >>> If we always generate same toasted byte sequences from the same raw >>> values, we don't need to detoast at all to compare the contents. >>> Is it possible or not? >> >> For bytea, it seems it would be possible. >> >> For text, I think locales may make that impossible. Aren't there >> locale rules where two different characters can "behave the same" when >> comparing them? I know in Swedish at least w and v behave the same >> when sorting (but not when comparing) in some variants of the locale. >> > Some string's comparation operations are binary now too. But it is > question what will be new with collate support. Right. We are using memcmp() in texteq and textne now. We consider collations only in <, <=, =>, > and compare support functions. So, I think there is no regression here as long as raw values and toasted byte sequences have one-to-one correspondence. -- Itagaki Takahiro
В списке pgsql-hackers по дате отправления: