| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: For full text indexing, which is better, tsearch2 or |
| Date: | 2003-11-28 20:37:00 |
| Message-ID: | 20031128203700.GA19831@gp.word-to-the-wise.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Nov 28, 2003 at 01:18:48PM +0800, Christopher Kings-Lynne wrote:
>
> >Any thoughts?
>
> Actually, I ran my tests using tsearch V1. I wonder if there has been
> some weird regression between tsearch 1 and 2?
Maybe. tsearch2 doesn't seem production ready in other respects
(untsearch2.sql barfs with 'aggregate stat(tsvector) does not exist'
and the openfts mailing list, where this would be more appropriate,
doesn't appear to exist according to sourceforge).
So, using the same data, modulo a few alter tables, I try tsearch, V1.
It's a little slower than V2, and again runs far faster without an
index than with it. Broken in the same way.
I have 7.2.4 running on a Sun box, so I tried that too, with similar
results. tsearch just doesn't seem to work very well on this dataset
(or any other large dataset I've tried).
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-11-30 09:46:30 | Re: For full text indexing, which is better, tsearch2 or |
| Previous Message | Tom Lane | 2003-11-28 17:55:38 | Re: simple left join slows query more than expected |