| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Include Lists for Text Search |
| Date: | 2007-09-10 12:28:27 |
| Message-ID: | 1189427307.4281.226.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2007-09-10 at 12:58 +0100, Heikki Linnakangas wrote:
> 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.
>
> I don't understand what you're proposing. We already have dict_synonym
> that you can use to accept a simple list of words.
How does that allow me to limit the number of words to a known list?
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-09-10 12:28:59 | Re: Include Lists for Text Search |
| Previous Message | Andrew Dunstan | 2007-09-10 12:16:35 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-09-10 12:28:59 | Re: Include Lists for Text Search |
| Previous Message | Pavan Deolasee | 2007-09-10 12:24:39 | Re: HOT patch - version 15 |