Re: lexemes in prefix search going through dictionary modifications - Mailing list pgsql-hackers

From Sushant Sinha
Subject Re: lexemes in prefix search going through dictionary modifications
Date
Msg-id 1319566517.2023.24.camel@dragflick
Whole thread Raw
In response to Re: lexemes in prefix search going through dictionary modifications  (Florian Pflug <fgp@phlo.org>)
Responses Re: lexemes in prefix search going through dictionary modifications
List pgsql-hackers
On Tue, 2011-10-25 at 19:27 +0200, Florian Pflug wrote:

> Assume, for example, that the postgres mailing list archive search used
> tsearch (which I think it does, but I'm not sure). It'd then probably make
> sense to add "postgres" to the list of stopwords, because it's bound to 
> appear in nearly every mail. But wouldn't you want searched which include
> 'postgres*' to turn up empty? Quite certainly not.

That improves recall for "postgres:*" query and certainly doesn't help
other queries like "post:*". But more importantly it affects precision
for all queries like "a:*", "an:*", "and:*", "s:*", 't:*', "the:*", etc
(When that is the only search it also affects recall as no row matches
an empty tsquery). Since stopwords are smaller, it means prefix search
for a few characters is meaningless. And I would argue that is when the
prefix search is more important -- only when you know a few characters.


-Sushant.







pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: patch for distinguishing PG instances in event log v2
Next
From: Alexander Korotkov
Date:
Subject: Re: GiST for range types (was Re: Range Types - typo + NULL string constructor)