From: "Graeme Merrall" <gbmerrall@aol.com>
To: <chriskl@familyhealth.com.au>,
	"Hackers" <pgsql-hackers@postgresql.org>
Cc: <pgsql-general@postgresql.org>, <pgsql-sql@postgresql.org>
Subject: Re: tsearch vs. fulltextindex
Date: Wed, 14 Aug 2002 14:53:46 +1000
Message-ID: <MMEKJDBHGFPPMNBALCOHOENICCAA.GBMerrall@aol.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <GNELIHDDFBOCMGBFGEFOIELACDAA.chriskl@familyhealth.com.au>


> I've just done some performance comparisons between contrib/fulltextindex
> and contrib/tsearch.  Even with every optimisation I can think of for
> fulltextindex, tsearch is 300 times faster ;)
>
> Plus it doesn't require a separate table or complicated queries.
>
> I think we should strongly encourage people to use tsearch instead of
> fulltextindex.  I hope to commit some change to fulltextindex in the near
> future, so I'll add a note to the readme then.
>

Ditto. We just replaced Oracle Context Search with tsearch and it's just as
good for what we were using it for and nicer to play with.
There's no scoring as far as I can see but I can live with that.

(and hello fellow aussie)

Cheers,
 Graeme