From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: website doc search is extremely SLOW |
Date: | 2004-01-01 01:01:15 |
Message-ID: | 200401010101.i0111Fw08826@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Marc G. Fournier wrote:
> On Wed, 31 Dec 2003, Bruce Momjian wrote:
>
> > > Out of everything I've found so far, mnogosearch is one of the best ... I
> > > just wish I could figure out where the bottleneck for it was, since, from
> > > reading their docs, their method of storing the data doesn't appear to be
> > > particularly off. I'm tempted to try their caching storage manager, and
> > > getting away from SQL totally, but I *really* want to showcase PostgreSQL
> > > on this :(
> >
> > Well, PostgreSQL is being un-showcased in the current setup, that's for
> > sure. :-(
>
> Agreed ... I could install the MySQL backend, whichits designed for, and
> advertise it as PostgreSQL? :)
I would be curious to know if it is faster --- that would tell use if it
is tuned only for MySQL.
Have you tried CLUSTER? I think the MySQL ISAM files are
auto-clustered, and clustering is usually important for full-text
searches.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2004-01-01 01:20:25 | Re: Bug and/or feature? Complex data types in tables... |
Previous Message | Marc G. Fournier | 2004-01-01 00:40:22 | Re: website doc search is extremely SLOW |