| From: | "Thomas Samson" <koollman(at)gmail(dot)com> |
|---|---|
| To: | "Ulrich Habel" <espero7757(at)gmx(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: query planner: automatic rescribe of LIKE to BETWEEN ? |
| Date: | 2006-08-22 18:21:23 |
| Message-ID: | 4e96c6600608221121p2afc603bx90fcf879aab47d96@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 8/22/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Ulrich Habel wrote:
> > Hello all,
> > had an idea of optimizing a query that may work generally.
> >
> > In case a 'column' is indexed, following two alterations could be done
> > I think:
> >
> > A)
> >
> > select ... where column ~ '^Foo' --> Seq Scan
>
> This is not true. You can make this query use an index if you create it
> with opclass varchar_pattern_ops or text_pattern_ops, as appropiate.
>
> Thus you don't need any hack here.
>
And in the case of more general expression, like:
select ... where column ~ 'something';
Is there a way to optimise this ? (in the case where 'something' is not
a word, but a part of a word)
--
Thomas SAMSON
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-08-22 18:49:57 | Re: query planner: automatic rescribe of LIKE to BETWEEN ? |
| Previous Message | Marinos Yannikos | 2006-08-22 18:10:49 | VACUUM FULL needed sometimes to prevent transaction ID wraparound? |