From: Tom Lane <tgl@sss.pgh.pa.us>
To: Artur Zakirov <a.zakirov@postgrespro.ru>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: Rethinking our fulltext phrase-search implementation
Date: Wed, 21 Dec 2016 09:30:07 -0500
Message-ID: <4361.1482330607@sss.pgh.pa.us> (raw)
In-Reply-To: <773bb687-1388-6c78-af23-5635a41a243d@postgrespro.ru>
References: <28215.1481999808@sss.pgh.pa.us>
<773bb687-1388-6c78-af23-5635a41a243d@postgrespro.ru>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Artur Zakirov <a.zakirov@postgrespro.ru> writes:
> Otherwise it seems that queries like 'a <-> (b & c)' will always return
> false. Then we need maybe some warning message.
Well, the query as written is pointless, but it could be useful with
something other than "b" and "c" as the AND-ed terms. In this usage
"&" is equivalent to "<0>", which we know has corner-case uses.
I'm not inclined to issue any sort of warning for unsatisfiable queries.
We don't issue a warning when a SQL WHERE condition collapses to constant
FALSE, and that seems like exactly the same sort of situation.
It strikes me though that the documentation should point this out.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, a.zakirov@postgrespro.ru
Subject: Re: Rethinking our fulltext phrase-search implementation
In-Reply-To: <4361.1482330607@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox