pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Graeme Merrall <gbmerrall@aol.com>
To: chriskl@familyhealth.com.au
To: Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: tsearch vs. fulltextindex
Date: Wed, 14 Aug 2002 14:53:46 +1000
Message-ID: <MMEKJDBHGFPPMNBALCOHOENICCAA.GBMerrall@aol.com> (raw)
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




view thread (4+ messages)

Message-ID: <MMEKJDBHGFPPMNBALCOHOENICCAA.GBMerrall@aol.com>
Permalink:  ../MMEKJDBHGFPPMNBALCOHOENICCAA.GBMerrall@aol.com/
Also on:    postgresql.org/message-id/MMEKJDBHGFPPMNBALCOHOENICCAA.GBMerrall@aol.com

 · 

reply

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-sql@postgresql.org
  Cc: gbmerrall@aol.com, chriskl@familyhealth.com.au, pgsql-hackers@postgresql.org, pgsql-general@postgresql.org
  Subject: Re: tsearch vs. fulltextindex
  In-Reply-To: <MMEKJDBHGFPPMNBALCOHOENICCAA.GBMerrall@aol.com>

* 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