Re: BUG #17125: Operator precedence bug in websearch_to_tsquery function

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "tim(dot)connolly(at)oovvuu(dot)com" <tim(dot)connolly(at)oovvuu(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17125: Operator precedence bug in websearch_to_tsquery function
Date: 2021-07-28 13:40:25
Message-ID: CAKFQuwa2v2F9spFbJgnDey9pNtk-R3TOOAJ1VU6fGTD5=Mm4DQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, July 27, 2021, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

>
> postgres=# select websearch_to_tsquery('english', 'foo bar or baz');
> websearch_to_tsquery
> -----------------------
> 'foo' & 'bar' | 'baz'
> (1 row)
>
> Expected: 'foo' & ('bar' | 'baz')
>
>
The documentation describes the operator precedence and it isn’t what you
expect.

https://www.postgresql.org/docs/current/datatype-textsearch.html#DATATYPE-TSQUERY

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-07-28 14:13:35 Re: BUG #17125: Operator precedence bug in websearch_to_tsquery function
Previous Message Etsuro Fujita 2021-07-28 08:28:09 Re: The case when AsyncAppend exists also in the qual of Async ForeignScan