Skip site navigation (1) Skip section navigation (2)

Re: Rethinking our fulltext phrase-search implementation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rethinking our fulltext phrase-search implementation
Date: 2016-12-17 21:15:37
Message-ID: 18847.1482009337@sss.pgh.pa.us (view raw or whole thread)
Thread:
Lists: pgsql-hackers
I wrote:
> It's worth noting that with these rules, phrase searches will act as
> though "!x" always matches somewhere; for instance "!a <-> !b" will match
> any tsvector.  I argue that this is not wrong, not even if the tsvector is
> empty: there could have been adjacent stopwords matching !a and !b in the
> original text.  Since we've adjusted the phrase matching rules to treat
> stopwords as unknown-but-present words in a phrase, I think this is
> consistent.  It's also pretty hard to assert this is wrong and at the same
> time accept "!a <-> b" matching b at the start of the document.

To clarify this point, I'm imagining that the patch would include
documentation changes like the attached.

			regards, tom lane


Attachment: ts-doc-changes.patch
Description: text/x-diff (2.6 KB)

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2016-12-17 21:17:45
Subject: Re: CREATE OR REPLACE VIEW bug
Previous:From: Corey HuinkerDate: 2016-12-17 20:39:22
Subject: Re: PSQL commands: \quit_if, \quit_unless

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group