Skip site navigation (1) Skip section navigation (2)

Re: For full text indexing, which is better, tsearch2 or

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Steve Atkins <steve(at)blighty(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: For full text indexing, which is better, tsearch2 or
Date: 2003-11-30 09:46:30
Message-ID: 3FC9BC76.2030308@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-performance
> 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).

Well, as I've shown - works fine for me...

I strongly suggest you repost your problem report to -hackers, since the 
fact that the tsearch developers haven't chimed in implies to me that 
they don't watch the performance list.

BTW, read this about Gist indexes:

http://www.postgresql.org/docs/current/static/limitations.html

(Note lack of concurrency)

Chris


In response to

Responses

pgsql-performance by date

Next:From: Kamalraj Singh MadhanDate: 2003-12-01 10:17:47
Subject: Dump restoration via archive files
Previous:From: Steve AtkinsDate: 2003-11-28 20:37:00
Subject: Re: For full text indexing, which is better, tsearch2 or

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group