Re: [HACKERS] Flexible configuration for full-text search

On Tue, 31 Oct 2017 09:47:57 +0100 Emre Hasegeli wrote: > > If we want to save this behavior, we should somehow pass a stopword > > to tsvector composition function (parsetext in ts_parse.c) for > > counter increment or increment it in another way. Currently, an > > empty

Re: [HACKERS] Flexible configuration for full-text search

On Mon, 6 Nov 2017 18:05:23 +1300 Thomas Munro wrote: > On Sat, Oct 21, 2017 at 1:39 AM, Aleksandr Parfenov > wrote: > > In attachment updated patch with fixes of empty XML tags in > > documentation. > > Hi Aleksandr, > > I'm not

Re: [HACKERS] Flexible configuration for full-text search

On Sat, Oct 21, 2017 at 1:39 AM, Aleksandr Parfenov wrote: > In attachment updated patch with fixes of empty XML tags in > documentation. Hi Aleksandr, I'm not sure if this is expected at this stage, but just in case you aren't aware, with this version of the patch

Re: [HACKERS] Flexible configuration for full-text search

> I'm mostly happy with mentioned modifications, but I have few questions > to clarify some points. I will send new patch in week or two. I am glad you liked it. Though, I think we should get approval from more senior community members or committers about the syntax, before we put more effort to

Re: [HACKERS] Flexible configuration for full-text search

I'm mostly happy with mentioned modifications, but I have few questions to clarify some points. I will send new patch in week or two. On Thu, 26 Oct 2017 20:01:14 +0200 Emre Hasegeli wrote: > To put it formally: > > ALTER TEXT SEARCH CONFIGURATION name > ADD MAPPING FOR

Re: [HACKERS] Flexible configuration for full-text search

> The patch introduces way to configure FTS based on CASE/WHEN/THEN/ELSE > construction. Interesting feature. I needed this flexibility before when I was implementing text search for a Turkish private listing application. Aleksandr and Arthur were kind enough to discuss it with me off-list