| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Charles Sprickman <spork(at)bway(dot)net>, Madison Kelly <linux(at)alteeve(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Writting a "search engine" for a pgsql DB |
| Date: | 2007-02-27 13:33:47 |
| Message-ID: | 45E4333B.9020008@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Magnus Hagander wrote:
>
> Just as a datapoint, we did try to use mnogosearch for the
> postgresql.org website+archives search, and it fell over completely.
> Indexing took way too long, and we had search times several thousand
> times longer than with tsearch2.
>
> That said, I'm sure there are cases when it works fine :-)
There are - in fact before your time the site did use Mnogosearch. We
moved to our own port of ASPSeek when we outgrew Mnogo's capabilities,
and then to your TSearch code when we outgrew ASPSeek.
When we outgrow PostgreSQL & Tsearch2, then, well, we'll need to stop
pretending to be Google...
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2007-02-27 13:56:08 | Re: Opinions on Raid |
| Previous Message | Magnus Hagander | 2007-02-27 13:15:58 | Re: Writting a "search engine" for a pgsql DB |