From: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Fwd: FTS |
Date: | 2014-05-05 15:15:19 |
Message-ID: | CAKFQuwaD3tgEvbTHKDFOCPwes-Tgz4r2rroqep3q8eBG-yDVVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Please reply to the list. Also, it is proper etiquette on this list to
bottom-post - just like my original reply.
Original response below.
---------- Forwarded message ----------
From: David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Date: Mon, May 5, 2014 at 11:12 AM
Subject: Re: [NOVICE] FTS
To: Jonatan Malaver <jon(dot)malaver(at)shrewsburyma(dot)gov>
"kva" thoughs the FTS query off. If I remove kva then it works. I'm
> looking for suggestions. Should I look for those keywords on the search
> string and remove them? Or is there a way to make postgres ignore it?
>
>
Create a custom dictionary configuration that defines the abbreviations as
"stop words" and use it to parse the input query.
http://www.postgresql.org/docs/9.3/interactive/textsearch-controls.html
12.3.2. Parsing Queries
to_tsquery([ config regconfig, ] querytext text) returns tsquery
The documentation is hopefully sufficiently helpful for describing how to
create a custom configuration and make use of it.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jonatan Malaver | 2014-05-05 15:16:49 | Re: FTS |
Previous Message | David G Johnston | 2014-05-05 14:32:36 | Re: FTS |