| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Ivan Voras <ivoras(at)fer(dot)hr> |
| Cc: | PFC <lists(at)boutiquenumerique(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: String matching |
| Date: | 2005-02-14 22:31:46 |
| Message-ID: | 20050214143050.R11070@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 14 Feb 2005, Ivan Voras wrote:
> Stephan Szabo wrote:
> > On Mon, 14 Feb 2005, Ivan Voras wrote:
>
> >>Could you give me an example for this, or point me to the relevant
> >>documentation?
>
> >
> > http://www.postgresql.org/docs/8.0/interactive/indexes-opclass.html
>
> Thanks! I didn't know this and I certainly didn't think it would be that
> easy :)
Well, it's not perfect. It requires a separate index from one for normal
comparisons, so it's trading modification speed for LIKE lookup speed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Aufflick | 2005-02-14 23:34:35 | seq scan cache vs. index cache smackdown |
| Previous Message | Ivan Voras | 2005-02-14 22:29:15 | Re: String matching |