RE: Possible solution for LIKE optimization

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Possible solution for LIKE optimization
Date: 2001-08-06 17:47:10
Message-ID: EKEJJICOHDIEMGPNIFIJOEDIFBAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> >> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Wait, why isn't that the solution in the first place. Let's build the
> > index with an opclass that uses plain strcmp comparison.
>
> > Do we have to make 2 indexes for non_ASCII text field ?
>
> You would if you want to use indexscans for both LIKE and "x < 'FOO'"
> (ie, locale-aware comparisons).

And ORDER BY ?

> Which is not great, but I think we've
> finally seen the light: a locale-sorted index is just plain not useful
> for LIKE.

I'm not familiar with non_ASCII locale.
Is 'ss' always guaranteed to be LIKE 's%' for example ?

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-08-06 18:31:27 Re: Possible solution for LIKE optimization
Previous Message Hiroshi Inoue 2001-08-06 17:46:58 RE: Re: AW: Re: OID wraparound: summary and proposal