Re: Improving FTS for Greek

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Improving FTS for Greek
Date: 2023-06-06 21:13:26
Message-ID: 0c05e7bd-22f7-ad8a-4ecb-a23ec84e27ff@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03.06.23 19:47, Florents Tselai wrote:
> There’s another previous relevant patch [0] but was never merged. I’ve
> included these stop words and added some more (info in README.md).
>
> For my personal projects looks like it yields much better results.
>
> I’d like some feedback on the extension ; particularly on the
> installation infra (I’m not sure I’ve handled properly the permissions
> in the .sql files)
>
> I’ll then try to make a .patch for this.

The open question at the previous attempt was that it wasn't clear what
the upstream source or long-term maintenance of the stop words list
would be. If it's just a personally composed list, then it's okay if
you use it yourself, but for including it into PostgreSQL it ought to
come from a reputable non-individual source like snowball.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-06-06 21:23:50 Re: [PATCH] pg_regress.c: Fix "make check" on Mac OS X: Pass DYLD_LIBRARY_PATH
Previous Message Andrew Gierth 2023-06-06 20:37:26 Re: Order changes in PG16 since ICU introduction