Thanks to visit codestin.com
Credit goes to postgrespro.com

Re: [HACKERS] Rethinking our fulltext phrase-search implementation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Rethinking our fulltext phrase-search implementation
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: [HACKERS] Rethinking our fulltext phrase-search implementation  (Artur Zakirov <[email protected]>)
List pgsql-hackers
Artur Zakirov <[email protected]> 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



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Why does plpython delay composite type resolution?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Why does plpython delay composite type resolution?