From: Dave Page <dpage@postgresql.org>
To: Magnus Hagander <magnus@hagander.net>
Cc: Charles Sprickman <spork@bway.net>
Cc: Madison Kelly <linux@alteeve.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Writting a "search engine" for a pgsql DB
Date: Tue, 27 Feb 2007 13:33:47 +0000
Message-ID: <45E4333B.9020008@postgresql.org> (raw)
In-Reply-To: <20070227131558.GP12721@svr2.hagander.net>
References: <45E30ADA.2050700@alteeve.com>
<Pine.OSX.4.64.0702261551070.289@white.nat.fasttrackmonkey.com>
<20070227131558.GP12721@svr2.hagander.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dpage@postgresql.org, magnus@hagander.net, spork@bway.net, linux@alteeve.com
Subject: Re: Writting a "search engine" for a pgsql DB
In-Reply-To: <45E4333B.9020008@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox