Re: Flexible configuration for full-text search

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: a(dot)parfenov(at)postgrespro(dot)ru, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Flexible configuration for full-text search
Date: 2018-11-29 13:02:16
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

> On Wed, Aug 29, 2018 at 10:38 AM Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru> wrote:
> On Tue, 28 Aug 2018 12:40:32 +0700
> Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru> wrote:
> >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.
> During work on the new version of the patch, I found an issue in
> proposed syntax. At the beginning of the conversation, there was a
> suggestion to split stop word filtering and words normalization. At this
> stage of development, we can use a different dictionary for stop word
> detection, but if we drop the word, the word counter wouldn't increase
> and the stop word will be processed as an unknown word.

Maybe it would be better if you or some of your colleagues (Alexander, Arthur?)
will post this new version, because the current one has some conflicts - so it
would be easier for a reviewers. For now I'll move it to the next CF.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-11-29 13:11:11 Re: pg_config wrongly marked as not parallel safe?
Previous Message Peter Eisentraut 2018-11-29 13:01:18 Re: PostgreSQL Limits and lack of documentation about them.