Work Around for Oracle Context Indexes?

David Griffiths wrote:

We're looking to replace Oracle with PostgresQL 7.2 sometime soon.

Both of our websites run Oracle, and one uses context indexes. These are
indexes on a table that contains text. A context index will create an index
on that column (minus irrelevant words like and/or/but/if/etc), and allow
searches to be done for a specific word.

Anyone offer a work-around to this?

Sure, see /contrib/fulltextindex.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In article <200202181429.g1IETjP12439@candle.pha.pa.us>,
Bruce Momjian <pgman@candle.pha.pa.us> wrote:

Sure, see /contrib/fulltextindex.

Is this bit from README.fti still true:

(this can also be done by using subselects - but subselects are currently
inefficient in Postgres, and maybe there're other ways too).

If not, would it be better to use joins or sub-selects?

mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

Sorry - the post that showed up this morning was old - I think it got
stalled by the software that manages the list. When I saw that it didn't
show up after I posted it, I reposted , and got a bunch of answers, and then
out of the blue my stalled post re-appears.

Thanks for the answers - there was some new info in there (so you didn't
waste your time).

David

----- Original Message -----
From: "Mike Castle" <dalgoda@ix.netcom.com>
Newsgroups: local.ml.postgresql.general
Sent: Monday, February 18, 2002 12:15 PM
Subject: Re: [GENERAL] Work Around for Oracle Context Indexes?

In article <200202181429.g1IETjP12439@candle.pha.pa.us>,
Bruce Momjian <pgman@candle.pha.pa.us> wrote:

Sure, see /contrib/fulltextindex.

Is this bit from README.fti still true:

(this can also be done by using subselects - but subselects are currently
inefficient in Postgres, and maybe there're other ways too).

If not, would it be better to use joins or sub-selects?

mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); --

gcc