Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Writting a "search engine" for a pgsql DB
- 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: Tue, 27 Feb 2007 13:33:47 +0000
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
- Follow-Ups:
- Re: Writting a "search engine" for a pgsql DB
- From: Steinar H. Gunderson
- Re: Writting a "search engine" for a pgsql DB
- From: Charles Sprickman
- Re: Writting a "search engine" for a pgsql DB
- References:
- Writting a "search engine" for a pgsql DB
- From: Madison Kelly
- Re: Writting a "search engine" for a pgsql DB
- From: Charles Sprickman
- Re: Writting a "search engine" for a pgsql DB
- From: Magnus Hagander
- Writting a "search engine" for a pgsql DB
- Prev by Date: Opinions on Raid
- Next by Date: Re: Opinions on Raid
- Previous by thread: Re: Writting a "search engine" for a pgsql DB
- Next by thread: Re: Writting a "search engine" for a pgsql DB
- Indexes: