Re: like/ilike improvements - Mailing list pgsql-hackers

From Tom Lane
Subject Re: like/ilike improvements
Date
Msg-id 21418.1179936430@sss.pgh.pa.us
Whole thread Raw
In response to Re: like/ilike improvements  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> I am also wondering if it might be sensible to make this choice once at 
> backend startup and store a function pointer, instead of doing it for 
> every string processed by like/ilike:

>     if (pg_database_encoding_max_length() == 1)
>         return SB_MatchText(s, slen, p, plen);
>     else if (GetDatabaseEncoding() == PG_UTF8)
>         return UTF8_MatchText(s, slen, p, plen);
>     else
>         return MB_MatchText(s, slen, p, plen);

> I guess that might make matters harder if we ever got per-column encodings.

Yeah.  It's not saving much anyway ... I wouldn't bother.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: like/ilike improvements
Next
From: Zdenek Kotala
Date:
Subject: Re: [GSOC] - I ntegrity check algorithm for data files