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

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

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Charles Sprickman <spork(at)bway(dot)net>
Cc: 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:15:58
Message-ID: 20070227131558.GP12721@svr2.hagander.net (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, Feb 26, 2007 at 04:24:12PM -0500, Charles Sprickman wrote:
> On Mon, 26 Feb 2007, Madison Kelly wrote:
> 
> >Hi all,
> >
> >I'd really like to come up with a more intelligent search engine that 
> >doesn't take two minutes to return results. :) I know, in the end good 
> >indexes and underlying hardware will be important, but a sane as possible 
> >query structure helps to start with.
> 
> I'm not a programmer, so I can't comment on how good of an example this 
> is, but I've been pretty happy with mnogosearch:
> 
> http://www.mnogosearch.com/
> 
> The *nix versions are free.  Looking at the db structure gave me a bit of 
> an idea of what I'm guessing is the "right way" to search a huge amount of 
> documents.

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 :-)

//Magnus

In response to

Responses

pgsql-performance by date

Next:From: Dave PageDate: 2007-02-27 13:33:47
Subject: Re: Writting a "search engine" for a pgsql DB
Previous:From: Joe UhlDate: 2007-02-27 13:12:00
Subject: Opinions on Raid

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