Re: texteq/byteaeq: avoid detoast [REVIEW] - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: texteq/byteaeq: avoid detoast [REVIEW]
Date
Msg-id AANLkTinB9=Yd_ci8=AZqOEk7Mr1Ze+L6k+ubpKbEbfoX@mail.gmail.com
Whole thread Raw
In response to Re: texteq/byteaeq: avoid detoast [REVIEW]  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: texteq/byteaeq: avoid detoast [REVIEW]  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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 by date:

Previous
From: Anssi Kääriäinen
Date:
Subject: Re: SSI patch version 12
Next
From: Peter Eisentraut
Date:
Subject: Re: texteq/byteaeq: avoid detoast [REVIEW]