Re: Support LIKE with nondeterministic collations - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support LIKE with nondeterministic collations
Date
Msg-id 2ab6ec19-f9a9-4960-81f8-54028afb496e@eisentraut.org
Whole thread Raw
In response to Re: Support LIKE with nondeterministic collations  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Support LIKE with nondeterministic collations
List pgsql-hackers
On 03.05.24 15:20, Robert Haas wrote:
> On Fri, May 3, 2024 at 4:52 AM Peter Eisentraut <peter@eisentraut.org> wrote:
>> What the implementation does is, it walks through the pattern.  It sees
>> '_', so it steps over one character in the input string, which is '.'
>> here.  Then we have 'foo.' left to match in the input string.  Then it
>> takes from the pattern the next substring up to but not including either
>> a wildcard character or the end of the string, which is 'oo', and then
>> it checks if a prefix of the remaining input string can be found that is
>> "equal to" 'oo'.  So here it would try in turn
>>
>>       ''     = 'oo' collate ign_punct ?
>>       'f'    = 'oo' collate ign_punct ?
>>       'fo'   = 'oo' collate ign_punct ?
>>       'foo'  = 'oo' collate ign_punct ?
>>       'foo.' = 'oo' collate ign_punct ?
>>
>> and they all fail, so the match fails.
> 
> Interesting. Does that imply that these matches are slower than normal ones?

Yes, certainly, and there is also no indexing support (other than for 
exact matches).




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Document NULL
Next
From: Tom Lane
Date:
Subject: Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation