Fwd: FTS
| От | David Johnston |
|---|---|
| Тема | Fwd: FTS |
| Дата | |
| Msg-id | CAKFQuwaD3tgEvbTHKDFOCPwes-Tgz4r2rroqep3q8eBG-yDVVg@mail.gmail.com обсуждение исходный текст |
| Ответ на | FTS (Jonatan Malaver <jon.malaver@shrewsburyma.gov>) |
| Ответы |
Re: FTS
|
| Список | 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.g.johnston@gmail.com>
Date: Mon, May 5, 2014 at 11:12 AM
Subject: Re: [NOVICE] FTS
To: Jonatan Malaver <jon.malaver@shrewsburyma.gov>
From: David Johnston <david.g.johnston@gmail.com>
Date: Mon, May 5, 2014 at 11:12 AM
Subject: Re: [NOVICE] FTS
To: Jonatan Malaver <jon.malaver@shrewsburyma.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.
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.
В списке pgsql-novice по дате отправления: