From: tomas@tuxteam.de
To: Tomasz Ostrowski <tometzky@batory.org.pl>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Subject: Re: query very slow when enable_seqscan=on
Date: Tue, 4 Jul 2006 16:24:34 +0000
Message-ID: <20060704162434.GD20619@www.trapp.net> (raw)
In-Reply-To: <20060704144406.GA21511@batory.org.pl>
References: <20060703203105.GA2801@batory.org.pl>
<7353.1151967946@sss.pgh.pa.us>
<20060704083733.GA20102@batory.org.pl>
<13853.1152021389@sss.pgh.pa.us>
<20060704144406.GA21511@batory.org.pl>
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
Attachments:
signature.asc (application/pgp-signature, 188B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tomas@tuxteam.de, tometzky@batory.org.pl, tgl@sss.pgh.pa.us, pgsql-bugs@postgresql.org
Subject: Re: query very slow when enable_seqscan=on
In-Reply-To: <20060704162434.GD20619@www.trapp.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox