| From: | Jonatan Malaver <jon(dot)malaver(at)shrewsburyma(dot)gov> |
|---|---|
| To: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: FTS |
| Date: | 2014-05-05 15:16:49 |
| Message-ID: | 58E13A9FA1D4994EB29384A8025A97B21BBF88A6@mbx027-e1-nj-6.exch027.domain.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Thanks! I’ll give that a try
From: David Johnston [mailto:david(dot)g(dot)johnston(at)gmail(dot)com]
Sent: Monday, May 05, 2014 11:13 AM
To: Jonatan Malaver
Subject: Re: [NOVICE] FTS
"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 | Jack Kaufman | 2014-05-05 15:27:37 | Re: FTS |
| Previous Message | David Johnston | 2014-05-05 15:15:19 | Fwd: FTS |