From: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, Dmitry Ivanov <d(dot)ivanov(at)postgrespro(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, David Steele <david(at)pgmasters(dot)net> |
Subject: | Re: [PATCH] Phrase search ported to 9.6 |
Date: | 2016-04-01 08:36:29 |
Message-ID: | CAF4Au4xtkJgCNRhuK80xLM=B5L7puz75NKcgE-QAHnrgQ4yRTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 31, 2016 at 9:14 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> What led you to choose the ? operator for the FOLLOWED BY semantics?
> It doesn't seem a terribly natural choice -- most other things seems to
> use ? as some sort of wildcard. What about something like "...", so you
> would do
> SELECT q @@ to_tsquery('fatal ... error');
> and
> SELECT q @@ (tsquery 'fatal' ... tsquery 'error');
>
>
originally was $, but then we change it to ?, we don't remember why. During
warming-up this morning we came to other suggestion
SELECT q @@ to_tsquery('fatal <> error');
and
SELECT q @@ to_tsquery('fatal <2> error');
How about this ?
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-04-01 08:39:43 | Re: Move PinBuffer and UnpinBuffer to atomics |
Previous Message | Andres Freund | 2016-04-01 08:35:18 | Re: Move PinBuffer and UnpinBuffer to atomics |