Full text search parser dictionary

From: Eugene Podshivalov <yaugenka(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Full text search parser dictionary
Date: 2019-02-07 22:44:35
Message-ID: CAEPw1JXu_gH5xoZiwJWL69hHvfv+=i5S1tXKMrijkg-HiHoNdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,
I have tried utilizing the full text searh feature and works as charm,
except for one think which I would like to suggest to improve.

When a document is split into tokens the parser removes any whitespace or
punctuation charactures not otherwise recognized. But some punctuation
charactures such as a dot, slash and hyphen may be used to denote
abbreviations and removing them from a token may result in changing the
meaning of a word.

Here are some examples from the Russian language.
1. Parsing "р-н" returns two separate meaningless charactures but the
combination denotes "район" (a district).
2. Parsing "с/с" returns two identical charactures which are later
recognized as stop words but the combination donotes "сельсовет" (a
subdistrict)
3. Parsing "o." returns a single characture which is later recognized as a
stop word but the conbination denotes "остров" (an island).

It would be nice to have a possibility to assign a dictionary to the parser
to recognize such cases.

Cheers,
Eugene

Browse pgsql-general by date

  From Date Subject
Next Message Justin Pryzby 2019-02-08 13:29:53 query logging of prepared statements
Previous Message David G. Johnston 2019-02-07 22:24:13 Re: Odd messages on reloading DB table