From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Problem with site doc search |
Date: | 2008-02-03 16:40:12 |
Message-ID: | 47A5EE6C.4040704@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Oleg Bartunov wrote:
> On Sat, 2 Feb 2008, Gurjeet Singh wrote:
>
>> Hi All,
>>
>> I just noticed a minor bug in our search results. Searching for
>> is_insteadbool in 8.3 docs returns the following page:
>>
>> http://www.postgresql.org/docs/8.3/static/catalog-pg-rewrite.html
>>
>> is_instead is a column, and bool is the datatype, both mentioned in
>> different columns. I know it is based on postgres' own full text
>> search, but
>> am not sure about the method how docs are read by the search engine. It
>> seems that the problem lies in the the way the doc was read and fed to
>> the
>> index builder, because the initial search results show these two words
>> combined.
>>
>> Also, is it possible to teach our search engine to *not* treat _
>> (underscore) as a word separator? This would be great help and would
>> result
>> much better results.
>
>
> Sure, there are many ways to do this. Magnus ?
Which way would you recommend? You're the tsearch master ;-)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2008-02-03 18:34:57 | Re: Truncate Triggers |
Previous Message | Peter Eisentraut | 2008-02-03 15:58:04 | Autoconf 2.61 |