Re: Missing feature in Phrase Search?

From: "Sven R(dot) Kunze" <srkunze(at)mail(dot)de>
To: Josh Berkus <josh(at)berkus(dot)org>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Missing feature in Phrase Search?
Date: 2017-05-04 21:23:56
Message-ID: 9223c966-321b-de92-a9f6-b18ee369331b@mail.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi everybody,

On 21.04.2017 20:47, Josh Berkus wrote:
> Oleg, Teodor, folks:
>
> I was demo'ing phrase search for a meetup yesterday, and the user
> feedback I got showed that there's a missing feature with phrase search.
> Let me explain by example:
>
>
> 'fix <-> error' will match 'fixed error', 'fixing error'
> but not 'fixed language error' or 'fixed a small error'
>
> 'fix <2> error' will match 'fixed language error',
> but not 'fixing error' or 'fixed a small error'
>
> 'fix <3> error' will match 'fixed a small error',
> but not any of the other strings.
>
>
> This is because the # in <#> is an exact match.
>
> Seems like we could really use a way for users to indicate that they
> want a range of word gaps. Like, in the example above, users could
> search on:
>
> 'fix <1:3> error'
>
> ... which would search for any phrase where "error" followed "fix" by
> between 1 and 3 words.
>
> Not wedded to any particular syntax for that, of course.

That could be useful. I would like to add another idea here about
leaving out one side of the range.

'fix <:3> error'
'fix <2:> error'

To either indicate 1 (left) or unbounded (right).

Sven

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2017-05-04 21:24:10 Re: CTE inlining
Previous Message Tom Lane 2017-05-04 21:13:37 Re: WITH clause in CREATE STATISTICS