Skip site navigation (1) Skip section navigation (2)

Re: Writting a "search engine" for a pgsql DB

From: Charles Sprickman <spork(at)bway(dot)net>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(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 23:36:11
Message-ID: Pine.OSX.4.64.0702271833470.289@white.nat.fasttrackmonkey.com (view raw or flat)
Thread:
Lists: pgsql-performance
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".

Thanks,

Charles

> When we outgrow PostgreSQL & Tsearch2, then, well, we'll need to stop
> pretending to be Google...
>
> /D
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

In response to

Responses

pgsql-performance by date

Next:From: Geoff TolleyDate: 2007-02-27 23:42:36
Subject: Re: Opinions on Raid
Previous:From: ChrisDate: 2007-02-27 23:05:42
Subject: Re: Writting a "search engine" for a pgsql DB

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group