Re: Stopgap solution for ILIKE in multibyte encodings

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stopgap solution for ILIKE in multibyte encodings
Date: 2006-09-04 17:41:25
Message-ID: 1d4e0c10609041041o7a93e6dfx848dc1e1a91cb69a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

On 9/4/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I propose that for ILIKE in multibyte encodings, we just pass the strings
> through lower() and then use the normal LIKE code. This will be a bit
> slower than what we do now, but as a wise man once said, code can be
> arbitrarily fast if it needn't give the right answer. And we can't just
> ignore the bug for still another release cycle.

Perhaps it's a stupid question but what about the indexes? An index on
lower(field) will be used by the new code or we wiil keep the current
behaviour of ILIKE?

Regards,

--
Guillaume

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2006-09-04 17:41:27 Re: [COMMITTERS] pgsql: sslinfo contrib module - information about current SSL
Previous Message Bruce Momjian 2006-09-04 17:39:31 Re: [PATCHES] Contrib module to examine client