DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=hUE8sEtTEmUb1x24J284N6FKOhnrvdDZ8PhMxr78xHeDo/MtRkYWKAyuFSTJdQBeKuMjTvpUYUGg20ErYNbbcFfs1lZm2JMffs5oX5aVAsGujunYkKwXjUc8q8hnbbCc5yeLL2mZhTmezvKNh0QTYUlaSvLzJorfLfeKurVs878=
Message-ID: <45E4B946.1060000@gmail.com>
Date: Wed, 28 Feb 2007 10:05:42 +1100
From: Chris <dmagick@gmail.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Madison Kelly <linux@alteeve.com>
CC: pgsql-performance@postgresql.org
Subject: Re: Writting a "search engine" for a pgsql DB
References: <45E30ADA.2050700@alteeve.com>
In-Reply-To: <45E30ADA.2050700@alteeve.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Madison Kelly wrote:
> Hi all,
> 
>   I am asking in this list because, at the end of the day, this is a 
> performance question.
> 
>   I am looking at writing a search engine of sorts for my database. I 
> have only ever written very simple search engines before which amounted 
> to not much more that the query string being used with ILIKE on a pile 
> of columns. This was pretty rudimentary and didn't offer anything like 
> relevance sorting and such (I'd sort by result name, age or whatnot).
> 
>   So I am hoping some of you guys and gals might be able to point me 
> towards some resources or offer some tips or gotcha's before I get 
> started on this. 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.

As someone mentioned, tsearch2 is a good option.

<plug> I wrote a small article about how to get it set up relatively 
easily: http://www.designmagick.com/article/27/ </plug>

-- 
Postgresql & php tutorials
http://www.designmagick.com/