| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | LIANHE SHAO <lshao2(at)jhmi(dot)edu> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: For full text indexing, which is better, tsearch2 or |
| Date: | 2003-11-27 00:51:14 |
| Message-ID: | 3FC54A82.2040605@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> Which one is better (performance/easier to use),
> tsearch2 or fulltextindex?
> there is an example how to use fulltextindex in the
> techdocs, but I checked the contrib/fulltextindex
> package, there is a WARNING that fulltextindex is
> much slower than tsearch2. but tsearch2 seems
> complex to use, and I can not find a good example.
> Which one I should use? Any suggestions?
I believe I wrote that warning :)
Tsearch2 is what you should use. Yes, it's more complicated but it's
HEAPS faster and seriously powerful.
Just read the README file.
You could also try out the original tsearch (V1), but that will probably
be superceded soon, now that tsearch2 is around.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-11-27 01:03:14 | Re: very large db performance question |
| Previous Message | Tom Lane | 2003-11-27 00:09:25 | Re: Followup - expression (functional) index use in joins |