From: | Chris <dmagick(at)gmail(dot)com> |
---|---|
To: | Madison Kelly <linux(at)alteeve(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Writting a "search engine" for a pgsql DB |
Date: | 2007-02-27 23:05:42 |
Message-ID: | 45E4B946.1060000@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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/
From | Date | Subject | |
---|---|---|---|
Next Message | Charles Sprickman | 2007-02-27 23:36:11 | Re: Writting a "search engine" for a pgsql DB |
Previous Message | Scott Marlowe | 2007-02-27 19:38:56 | Re: Two hard drives --- what to do with them? |