From: Magnus Hagander <magnus@hagander.net>
To: Charles Sprickman <spork@bway.net>
Cc: Dave Page <dpage@postgresql.org>
Cc: Madison Kelly <linux@alteeve.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Writting a "search engine" for a pgsql DB
Date: Wed, 28 Feb 2007 08:44:39 +0100
Message-ID: <20070228074439.GA24046@svr2.hagander.net> (raw)
In-Reply-To: <Pine.OSX.4.64.0702271833470.289@white.nat.fasttrackmonkey.com>
References: <45E30ADA.2050700@alteeve.com>
<Pine.OSX.4.64.0702261551070.289@white.nat.fasttrackmonkey.com>
<20070227131558.GP12721@svr2.hagander.net>
<45E4333B.9020008@postgresql.org>
<Pine.OSX.4.64.0702271833470.289@white.nat.fasttrackmonkey.com>
On Tue, Feb 27, 2007 at 06:36:11PM -0500, Charles Sprickman wrote:
> On Tue, 27 Feb 2007, Dave Page wrote:
>
> >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.
>
> At risk of pulling this way too far off topic, may I ask how many
> documents (mail messages) you were dealing with when things started to
> fall apart with mnogo? We're looking at it for a new project that will
> hopefully get bigger and bigger. We will be throwing groups of mailing
> lists into their own mnogo config/tables... If we should save ourselves
> the pain and look at something more homebrew, then we'll start
> investigating "Tsearch".
I don't know when it broke exactly, but I know we're currently doing
about 600,000 documents. AFAIK it started to fall apart pretty long
before that.
//Magnus
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: magnus@hagander.net, spork@bway.net, dpage@postgresql.org, linux@alteeve.com
Subject: Re: Writting a "search engine" for a pgsql DB
In-Reply-To: <20070228074439.GA24046@svr2.hagander.net>
References: <45E30ADA.2050700@alteeve.com> <Pine.OSX.4.64.0702261551070.289@white.nat.fasttrackmonkey.com> <20070227131558.GP12721@svr2.hagander.net> <45E4333B.9020008@postgresql.org> <Pine.OSX.4.64.0702271833470.289@white.nat.fasttrackmonkey.com> <20070228074439.GA24046@svr2.hagander.net>
* 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