From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Include Lists for Text Search |
Date: | 2007-09-10 12:10:26 |
Message-ID: | Pine.LNX.4.64.0709101557220.2767@sn.sai.msu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, 10 Sep 2007, Simon Riggs wrote:
> It seems possible to write your own functions to support various
> possibilities with text search.
>
> One of the more common thoughts is to have a list of words that you
> would like to include, i.e. the opposite of a stop word list.
>
> There are clear indications that indexing too many words is a problem
> for both GIN and GIST. If people already know what they'll be looking
> for and what they will never be looking for, it seems easier to supply
> that list up front, rather than hide it behind lots of hand-crafted
> code.
>
> Can we include that functionality now?
This could be realized very easyly using dict_strict, which returns
only known words, and mapping contains only this dictionary. So,
feel free to write it and submit.
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru)
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-09-10 12:12:09 | Re: integrated tsearch doesn't work with non utf8 database |
Previous Message | Heikki Linnakangas | 2007-09-10 11:58:07 | Re: Include Lists for Text Search |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-09-10 12:16:35 | Re: invalidly encoded strings |
Previous Message | Pavan Deolasee | 2007-09-10 11:58:22 | Re: HOT patch - version 15 |