Re: Adding an alternate syntax for Phrase Search

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Josh berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Adding an alternate syntax for Phrase Search
Date: 2016-05-23 02:13:03
Message-ID: CAKFQuwYhxhJ1vSX1sJJcUR=bRpL6M5ow__+BAbHY2o8872NUZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 22, 2016 at 6:53 PM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:

>
> to_tsquery(' Berkus & "PostgreSQL Version 10.0" ')
>>
>> ... would be equivalent to:
>>
>> to_tsquery(' Berkus & ( PostgreSQL <-> version <-> 10.0 )')
>>
>
> select to_tsquery('Berkus') && phraseto_tsquery('PostgreSQL Version 10.0');
> does it as you wish

​Sure, but I imagine (not having used it myself), that in cases involving
user input said text treated somewhat holistically and it wouldn't be all
that easy, or desirable, to choose between the two forms at runtime.

David J.​

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-05-23 02:18:58 Re: 9.4 failure on skink in _bt_newroot/XLogCheckBuffer
Previous Message David G. Johnston 2016-05-23 02:09:25 Re: Changed SRF in targetlist handling