Re: full text searching

From: Gunnar R|nning <gunnar(at)candleweb(dot)no>
To: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
Cc: "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>, Mitch Vincent <mitch(at)venux(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: full text searching
Date: 2001-02-08 15:36:24
Message-ID: x6bssdrxtz.fsf@thor.candleweb.no
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> writes:

> Sometimes I want it literal too. e.g. I'm searching for car I want car and
> nothing else.

Of course, you want this as well.

> In the end it seems too complex. I'm starting to think it may be better to
> keep things literal but fast, and do the smart stuff at the client (do
> multiple searches if necessary).

You got commercial products like Verity that is able to these kind of
things. I've used Verity in conjunction with Sybase, apart from stability
problems, that was a very nice combination on doing free text searches. I
could define which columns I wanted indexed, and then I could do you joins
against a proxy table(the index) to do synonym searches, word searches,
regex searches, soundex searches etc.

Verity was running in a separate process and that Sybase forwards the free
text search to when you join against the proxy table. Maybe we could have a
similar architecture in PostgreSQL as well some day.

Does anybody know how Oracle has implemented their "context" search or
whatever it is called nowadays ?

regards,

Gunnar

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-02-08 15:41:45 Re: tuples too big
Previous Message Lamar Owen 2001-02-08 15:30:37 Re: tuples too big

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-02-08 15:44:38 Re: Re: preproc.y error
Previous Message Tom Lane 2001-02-08 15:33:47 Re: Re: preproc.y error