From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Problem with site doc search |
Date: | 2008-02-02 13:18:39 |
Message-ID: | 65937bea0802020518x36c2e27bs727ba55c5bd227ed@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Thanks and best regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | indiatimes | yahoo }.com
EnterpriseDB http://www.enterprisedb.com
17° 29' 34.37"N, 78° 30' 59.76"E - Hyderabad
18° 32' 57.25"N, 73° 56' 25.42"E - Pune
37° 47' 19.72"N, 122° 24' 1.69" W - San Francisco *
Mail sent from my BlackLaptop device
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2008-02-02 13:41:41 | Re: Strange behavior on plpgsql trigger function in if comparison |
Previous Message | Stefan Kaltenbrunner | 2008-02-02 11:50:04 | Re: Strange behavior on plpgsql trigger function in if comparison |