Re: Full Text Index disk space requirements - Mailing list pgsql-performance

From
Subject Re: Full Text Index disk space requirements
Date
Msg-id 61777.12.249.229.112.1038341633.squirrel@www.l-i-e.com
Whole thread Raw
In response to Re: Full Text Index disk space requirements  (Maarten Boekhold <Maarten.Boekhold@reuters.com>)
Responses Re: Full Text Index disk space requirements  (Hannu Krosing <hannu@tm.ee>)
List pgsql-performance
> ps. are you trying to use the stuf from the 'fulltextindex' directory in
>  contrib/?

Yes.

> I originally wrote this as an experiment, and it actually
> turned  out not to be fast enough for my purpose. I've never done
> anything with  full text indexing again, but I believe that currently
> there are better  solutions based on PostgreSQL (i.e. OpenFTI?)

Oh.  ...

In case anybody finds these archived, it's OpenFTS:
http://sourceforge.net/projects/openfts/

Perhaps my question should be "What's the best full-text-index solution?"

Too open-ended?

PostgreSQL 7.1.3 (upgrading is not out of the question, but...)
~20,000 text articles scanned with OCR from _The Bulletin of the Atomic
Scientists_ (the Doomsday Clock folks)
Average text length: 9635 characters
    Max text length: 278227
Only 2000 of the texts are null or '', and those are probably "buglets"

Any other pertinent facts needed?




pgsql-performance by date:

Previous
From: Robert Treat
Date:
Subject: Re: performance of insert/delete/update
Next
From: Hannu Krosing
Date:
Subject: Re: Full Text Index disk space requirements