> On Tue, 18 Apr 2000, Bruce Momjian wrote:
>
> > > I agree! The last bit of advice given in the full text README. As I
> > > said, I'd built full-text stuff for experimentation (I had maybe 30k of
> > > raw text, which amounted to several 100,000 indexed entries), and I had
> > > clustered it, and it was pretty darn fast, even on a Pentium 233 with only
> > > 48 megs of RAM. I have significantly better hardware to run it on now.
> > > The original project called MySQL, but it just didn't have what we needed
> > > to put something like this together.
> >
> > With the original author, testing was fast, but when he loaded all the
> > data, it got very slow. The problem was that as soon as his data
> > exceeded the buffer cache, performance became terrible.
>
> How much data are we talking here? How can one get around this buffer
> cache problem?
>
You would have to fit _all_ your heap data into the PostgreSQL buffer
cache. That is a lot of shared memory. If it was that small, you
wouldn't need full-text indexing. :-)
--
Bruce Momjian | http://www.op.net/~candle
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