| From: | Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Flexible configuration for full-text search |
| Date: | 2018-08-28 05:40:32 |
| Message-ID: | 20180828124032.3d7db2bf@asp437-ThinkPad-L380 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 24 Aug 2018 18:50:38 +0300
Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
>Agreed, backward compatibility is important here. Probably we should
>leave old dictionaries for that. But I just meant that if we
>introduce new (better) way of stop words handling and encourage users
>to use it, then it would look strange if default configurations work
>the old way...
I agree with Alexander. The only drawback I see is that after addition
of new dictionaries, there will be 3 dictionaries for each language: old
one, stop-word filter for the language, and stemmer dictionary.
Also, the new approach will solve ambiguity in case of 'simple'
dictionary. Currently, it filters stop-words for the language, which
was selected during DB initialization.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-08-28 05:45:50 | Re: First steps to being a contributer |
| Previous Message | Andres Freund | 2018-08-28 05:08:33 | Re: BUG #15346: Replica fails to start after the crash |