Re: query very slow when enable_seqscan=on

From: tomas(at)tuxteam(dot)de
To: Tomasz Ostrowski <tometzky(at)batory(dot)org(dot)pl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: query very slow when enable_seqscan=on
Date: 2006-07-04 16:24:34
Message-ID: 20060704162434.GD20619@www.trapp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

On Tue, Jul 04, 2006 at 04:44:08PM +0200, Tomasz Ostrowski wrote:
> On Tue, 04 Jul 2006, Tom Lane wrote:
>
> > I think the real problem here is that regex matching is the wrong
> > tool for the job. Have you looked into a full-text index
> > (tsearch2)?
>
> So much to do with so little time...

For what it's worth, I've got pretty good results (at least taking the
little amount of work I put into it) with trigram indexes, courtesy of
$PGCONTRIB/pg_trgm.sql, just another amazing little piece by Bartunov
and Sigaev.

Let me know if you'd like to hear more.

Regards
-- tomás

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message tommaso gastaldi 2006-07-04 17:00:18 BUG #2513: What? OleDbSchemaGuids not supported ?!!! This is CRUCIAL!
Previous Message Tomasz Ostrowski 2006-07-04 14:44:08 Re: query very slow when enable_seqscan=on

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2006-07-04 18:15:54 Re: query very slow when enable_seqscan=on
Previous Message Nolan Cafferky 2006-07-04 16:18:43 Re: how to tune this query.