From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql@tomd.cc
cc: pgsql-bugs@postgresql.org, Oleg Bartunov <obartunov@gmail.com>,
        Teodor Sigaev <teodor@sigaev.ru>
Subject: Re: BUG #14515: tsquery with only a negative term doesn't match empty
 tsvector
In-reply-to: <20170126025524.1434.97828@wrigleys.postgresql.org>
References: <20170126025524.1434.97828@wrigleys.postgresql.org>
Comments: In-reply-to pgsql@tomd.cc
	message dated "Thu, 26 Jan 2017 02:55:24 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30720.1485401548.1@sss.pgh.pa.us>
Date: Wed, 25 Jan 2017 22:32:28 -0500
Message-ID: <30721.1485401548@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

pgsql@tomd.cc writes:
> Basically while `select 'somethingelse'::tsvector @@ '!foo'::tsquery`
> returns true, `select ''::tsvector @@ '!foo'::tsquery` returns false, which
> was surprising to me.

Not sure about this.  A plausible reading of '!foo' is "there is a lexeme
that is not foo".  But even if that was Oleg & Teodor's intention,
I would not want to swear that the tsquery stuff is totally consistent
about it ...

			regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs